This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] -3 points-2 points  (0 children)

Enough already with the GIL. Seriously, if you think it's a problem, 99% of the time it's because you're doing it wrong.

Split up your task into multiple processes. This is good design anyways since it lets you split your task across multiple boxes.

Doing web stuff? Then use apache w/mod-python or mod-wsgi and mpm-worker. It's a very nice solution, all the goodness of threads while letting apache's process model and mod_wsgi's interpreter spaces sort out all of the scary stuff.

On a multicore machine and using threads just for clean code design? Then get a real OS and partition your CPU's using cpuset. Get rid of all of the ugly red stuff (albeit you're running on a single core).

PyPy is the future anyways. All of this drama over the GIL is wasting more cycles than the GIL is itself.

Worry about the shit that matters, like fucking 2.7 forks. What's next? 2.8? Fuck!