Free-threaded/noGIL Python 3.13t testing experiment #659
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hoping that this fixes the issue when installing Python 3.13t on macOS
agriyakhetarpal
force-pushed
the
feat/free-threading-tests
branch
from
ecd7545 to
63acff1
Compare
agriyakhetarpal
force-pushed
the
feat/free-threading-tests
branch
from
00e60c8 to
55ab962
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Tip
This description is a stub and shall be updated soon.
This PR is on top of the changes from #643. Here, I'm trying to test against the free-threaded Python interpreter (Python 3.13t) and nightly wheels for SciPy and NumPy where we have free-threaded. This helps check two items: i. bugs in NumPy and SciPy related to free-threading to report upstream; and ii. whether we have anything of concern in our implementation in case there is nothing to report upstream.
It is to be noted that we are following the approach suggested by https://py-free-threading.github.io here; there is more testing to be done before I can mark this as ready for review: https://py-free-threading.github.io/porting/#validating-thread-safety-with-testing