3 ms·
SO, why would people be against removal of GIL ?
by ilyt 3y ago
SO, why would people be against removal of GIL ?
- throw16180339 3y agoHere are some possible reasons. They use unmaintained C extensions that won't be updated. They maintain C extensions that would be complex or painful to update. They're concerned about fragmenting the ecosystem into GIL and No GIL. They think that it will make single-threaded Python programs slower. They have no interest in multithreaded Python and don't think the additional complexity is justified.
- wheelerof4te 3y ago> They use unmaintained C extensions that won't be updated. Well, that's on them. > They're concerned about fragmenting the ecosystem into GIL and No GIL. Same way we have fragmentated ecosystem into ASYNC vs SYNC now? /s > They think that it will make single-threaded Python programs slower. Python is already horribly slow. A little bit slower single thread programs shouldn't be a problem. But the inability to run multi-threaded programs effectively in this day and age is very much a problem.
- zzzeek 3y agoI haven't fully confirmed this but my understanding is the proposal forks the ABI into two versions. which IIUC means any package with native extensions needs to release 2x as many wheel files (not to mention if I need to have two versions of the interpreter installed to build them, not sure though). seems like a mess