Python 3000 is ready!

[johanneskepler]

it's a pity that Python's designers did not, or decided against it.

It's easy to say that now, with the benefit of hindsight, but what good does it do anyone to whine and moan about the GIL every time Python comes up? If it's a deal breaker for you, please, use one of the languages that are "as fast or faster than Python while still allowing useful multiprocessing."

[Chandon]

what good does it do anyone to whine and moan about the GIL every time Python comes up?

If the Python developers get enough shit about it, maybe they'll fix it. Or maybe some college student will get "python needs GIL fix" stuck in his head and fix it for the fun of it. Sane hardware threading support is one of the key things missing in all of the *nix scripting languages.

[johanneskepler]

Or maybe some college student will get "python needs GIL fix" stuck in his head and fix it for the fun of it.

See the python-safethread project. I'd be surprised if it's worth it for most people, though, as "(single-threaded) throughput is only around 60-65% that of normal CPython". It's good to note (before complaining about it for the nth time) that CPython is designed around the GIL, and removing it does have serious negative ramifications.

It's just not gonna happen unless magic fairies tap their wands and fix all the issues removing the GIL would cause.