-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
GIL section of the FAQ is outdated (or shortly to be outdated) #114756
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
Labels
Comments
Possibly also should be tagged |
colesbury
pushed a commit
that referenced
this issue
Feb 6, 2024
Update FAQ section on removing the GIL to reflect recent progress on PEP 703 and PEP 684. Co-authored-by: AN Long <[email protected]>
Yes, I think so. I'll close this. |
fsc-eriker
pushed a commit
to fsc-eriker/cpython
that referenced
this issue
Feb 14, 2024
Update FAQ section on removing the GIL to reflect recent progress on PEP 703 and PEP 684. Co-authored-by: AN Long <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Documentation
https://docs.python.org/3.13/faq/library.html#can-t-we-get-rid-of-the-global-interpreter-lock (link is to the current alpha version)
Obviously work is in progress to remove the GIL which isn't reflected in the FAQ yet.
Also the second option:
If I understand correctly, interpreters with an isolated GIL are now at least partially implemented in a release version and again this isn't reflected in the FAQ.
Linked PRs
The text was updated successfully, but these errors were encountered: