This repository was archived by the owner on Jul 26, 2026. It is now read-only.
Add CI test job for no-GIL (free-threaded) Python 3.13 - #61
Merged
EliahKagan merged 1 commit intoMay 30, 2025
Merged
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
See gitpython-developers/GitPython#2005, and gitpython-developers/gitdb#122 for rationale. In short, if the corresponding check starts to fail in GitPython, it may be useful to observe if there is a failure here as well.
EliahKagan
marked this pull request as ready for review
May 30, 2025 20:53
Copy link
Copy Markdown
Member
Author
|
As in gitpython-developers/gitdb#122 (comment), I've fixed the title--no-GIL Python is called free-threaded, not "threaded"--even though the effect of doing so is fairly minimal. |
Sorry, something went wrong.
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
See gitpython-developers/GitPython#2005, and gitpython-developers/gitdb#122 for rationale. In short, if the corresponding check starts to fail in GitPython, it may be useful to observe if there is a failure here as well.