Eric Snow <ericsnowcurren...@gmail.com> added the comment:
On Sun, Feb 2, 2020 at 2:53 PM Raymond Hettinger <rep...@bugs.python.org> wrote: > Is the sub-interpreter PEP approved? PEP 554 is not approved yet (and certainly is not guaranteed, though I'm hopeful). However, that PEP is exclusively about exposing subinterpreters in the stdlib. There is no PEP for the effort to isolate subinterpreters and stop sharing the GIL between them. We are not planning on having such a PEP since the actual proposal is so basic ("make the GIL per-interpreter") and there has been no controversy. I need to do a better job about communicating the difference, as folks keep conflating PEP 554 with the effort to stop sharing the GIL between subinterpreters. Note that both are part of my "multi-core Python" project. [1] > If not, I had thought the plan was to only > implement PRs that made clean-ups that would have been necessary anyway. Right. In this case the "cleanup" is how singletons are finalized when the runtime shuts down. This has a material impact on projects that embed the CPython runtime. Currently runtime finalization is a mess. That said, making the singletons per-interpreter isn't a prerequisite of that cleanup. For specific case of the per-interpreter GIL world, we just need an approach that addresses their life cycle in a thread-safe way. [1] https://github.com/ericsnowcurrently/multi-core-python ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue39511> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com