Status of Python threading support (GIL removal)?

[OdarR]

On 19 juin, 11:52, Jure Erznožnik <jure.erznoz... at gmail.com> wrote:
> See here for introduction:http://groups.google.si/group/comp.lang.python/browse_thread/thread/3...
>
> Digging through my problem, I discovered Python isn't exactly thread
> safe and to solve the issue, there's this Global Interpreter Lock
> (GIL) in place.
> Effectively, this causes the interpreter to utilize one core when
> threading is not used and .95 of a core when threading is utilized.
>
> Is there any work in progess on core Python modules that will
> permanently resolve this issue?
> Is there any other way to work around the issue aside from forking new
> processes or using something else?

hi,

please read this carefully,
<http://www.ibm.com/developerworks/aix/library/au-multiprocessing/
index.html?ca=dgr-lnxw07Python-
Multi&S_TACT=105AGX59&S_CMP=grsitelnxw07>

there is a solution for Python on multi-core : multiprocessing api.
Really nice.
<http://docs.python.org/library/functions.html>
Keep real threads for common tasks like network stuff for example.

I recently complained too :-)
<http://groups.google.com/group/comp.lang.python/browse_frm/thread/
dbe0836d9602f322#>


Olivier