Overview

Python 3.12 is probably starting to support a no-gil configuration. PySide should to find the necessary changes to enable that in the PySide project. The anticipated community reaction
is quite huge, since that will make Python really performant.

Currently, there is only a prototype implementation that we are using. It is based on Python nogil-3.9.10-1 with a register machine and different opcodes. This version is by no means the version expected for the fall, when Python 3.12 should come into existence with NoGIL.

It is not clear whether this branch will be continued at all. This depends very much
on business decisions. I just wanted to make sure of the feasibility, but I'm not implementing it yet.
The feasibility is definitely there if they have the right people and time.

Areas in need of thread protection

(to be identified by thread sanitizer).

• Potentially many areas in Object deletion (reuse wrapper map lock?)
• libshiboken setParent()/ removeParent() and destruction maintaining lists of children and pointer to parent in SbkObjectPrivate/ParentInfo
• Signal/Slot ConnectionHash in sources/pyside6/libpyside/dynamicslot.cpp:303
• setNextQObjectMemoryAddr() sources/pyside6/libpysideqml/pysideqmlregistertype.cpp:41 (thread_local?)

References

• What’s New In Python 3.13
• PEP 703 – Making the Global Interpreter Lock Optional in CPython
• py-free-threading.github.io
• Free threaded vs Limited
• is-free-threading-our-only-option/subinterpreters