So - there is this PEP 684 related commit now -
“”"
commit 5c9ee49…
Author: Eric Snow ericsnowcurrently@gmail.com
Date: Mon May 8 13:15:09 2023 -0600
gh-99113: A Per-Interpreter GIL! (gh-104210)
This is the culmination of PEP 684 (and of my 8-year long multi-core Python project)!
Each subinterpreter may now be created with its own GIL (via Py_NewInterpreterFromConfig()). If not so configured then the interpreter will share with the main interpreter–the status quo since subinterpreters were added decades ago. The main interpreter always has its own GIL and subinterpreters from Py_NewInterpreter() will always share with the main interpreter.
“”"
Should PEP 554 be updated so one can choose which mode will a new sub-interpreter start? Or should it default to no-shared GIL interpreter ? (Seems to make sense)
Also, PEP 554 is still the cherry on top of PEP 684 which allows it to be used by Pythonistas everywhere - and it’s not been approved, even transitionally.
I will probably be able to provide my package on top of the transitional __xxsubinterpreters
which’s been merged, nonetheless - but maybe the fact that’s been merged should be mentioned on the PEP 554 text anyway.