3 ms·
Weren't a Python project called interpreters that had the aim of allowing different interpreters of Python, thus mitigating the the issues the GIL causes?
by happy_path 5y ago
Weren't a Python project called interpreters that had the aim of allowing different interpreters of Python, thus mitigating the the issues the GIL causes?
- BiteCode_dev 5y agoYes, a first version has been released, but it still needs a lot of ironing.
- happy_path 5y agoAwesome! Would it be ready for the next version?
- BiteCode_dev 5y agoUnlikely. The module is usable, and you can already import it and run it. But the perf benefit are still not there.
- germandiago 5y agoWhat is this module about actually? I mean, is it a model to run code in parallel in some way different to multiprocessing?
- BiteCode_dev 5y agoFor now it's only at the c level, with a python api in discussion: https://www.python.org/dev/peps/pep-0554/ https://www.python.org/dev/peps/pep-0554/ The idea is that the python code interpreter would not rely on global variables anymore, so that you can instantiate it several times. The GIL is tied to the interpreter, meaning 2 threads in 2 different interpreters do not share a gil, and can be schedule on different CPU.
- frakkingcylons 5y agoThat project is mentioned in the article.