Fix thread init for Python 3.9+ #10
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
PyEval_ThreadsInitialized()call behind aPY_VERSION_HEX < 0x03090000check.PyEval_InitThreads()unconditionally on Python ≥3.9, wherePyEval_ThreadsInitialized()was removed, keeping the GIL initialisation behaviour intact.Motivation
Python 3.9 removed
PyEval_ThreadsInitialized(), causing PySysC to fail at import/build time on modern interpreters with:AttributeError: module 'cpython' has no attribute 'PyEval_ThreadsInitialized'
The new guard allows PySysC to run on Python 3.9+ without regressing older Python releases.