-
-
Notifications
You must be signed in to change notification settings - Fork 164
Add no-GIL support #267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
clin1234
wants to merge
11
commits into
frida:main
Choose a base branch
from
clin1234:nogil
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+8
−6
Open
Add no-GIL support #267
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
37ca658
Disable building for limited API with no-GIL interpreters
clin1234 c9d437c
Update setup.py
clin1234 f1235f4
Fix minor oops
clin1234 a210958
FIx minor oops
clin1234 6285cec
Another try
clin1234 1969b49
Delete setup.cfg
clin1234 8b9ece6
Call PyUnstable_Module_SetGIL
clin1234 4842cb3
Do not build extension.c with limited API
clin1234 ec21403
Extremely silly spelling fix
clin1234 e2ef84d
Update frida/_frida/extension.c
clin1234 449688e
Restore building extension with limited API for now
clin1234 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
This file was deleted.
Oops, 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems like a regression, unless I'm missing something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that you ask, maybe that is no longer needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason we have it is so we can build a single binary (per OS/ABI combo) that works on older Python runtimes even when the build machine has a newer Python; without accidentally regressing on the range of versions supported.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to be sure, can you run workflows on your side to catch whatever regression that may arise from this PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's no point; I went through some pain to transition frida-python to the limited API, because it solved some long-standing issues. Nothing changed there. We cannot drop this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair enough: https://peps.python.org/pep-0803/ means that free-threaded wheels will have stable ABI starting in 3.15...