2 ms·
IMO, keeping the GIL is a good thing for Python. A language shouldn’t try to be all things to all people. If you are really craving performance and fully explo
by RcouF1uZ4gsC 3y ago
IMO, keeping the GIL is a good thing for Python.
A language shouldn’t try to be all things to all people. If you are really craving performance and fully exploiting all the resources of a CPU, Python is really not the language you are looking for. Multithreading brings in a lot of complexity, not only for the user, but also for the library implementer who may then have to worry about things they did not have to before.
Removing the GIL increases complexity and doesn’t provide any benefit to the vast majority of Python users and scripts.