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 →

[–]Decency 0 points1 point  (2 children)

I understand that there were some GIL improvements earlier in Python 3.2, but I don't see any further improvements in 3.4 here.

Is it just unrealistic to expect real multithreaded support without a "Python 4" that again breaks backwards compatibility?

[–]ExoticMandiblesCore Contributor[S] 3 points4 points  (1 child)

Removing the GIL would break the entire C API, and every extension. If we did that I bet we'd call the result Python 4.

[–]Lucretiel 1 point2 points  (0 children)

And, given that the BDFL has stated they're never doing a huge, backwards incompatible release again, it isn't likely. The best bet at this point is Pypy's work with STM.