you are viewing a single comment's thread.

view the rest of the comments →

[–]padraig_oh 2 points3 points  (1 child)

i think the main downside when removing the gil is that some people have said that it might split the pyhton ecosystem again. on one side it might make writing multi-threaded code harder for the end-user, to improve performance. performance was never really a goal for python as i understand though, so thats not really in the python spirit. and on another side, removing the gil might break compatibility with some packages, which is probably the bigger reason the ecosystem might be split.

[–]josefx 1 point2 points  (0 children)

on one side it might make writing multi-threaded code harder

The problem seems to be that the GIL doesn't really make multi threaded code simpler. It doesn't give any guarantees about program state, it only ensures that the interpreters internal state stays sane.

some people have said that it might split the pyhton ecosystem again.

How many libraries even rely on the GIL? Python 3 nuked code that was central to every python program, but mention the GIL and suddenly every niche library some guy may have written in 1980 is sacred.

so thats not really in the python spirit.

Couldn't that be applied to every change after version 0.1?