-
-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Rename Py_NOGIL
to a positive term
#111863
Comments
Maybe it will affect to #111571, Sam may need to make decision what should go first :) |
Yep, fully defer to Sam to merge things in whatever order he likes, including closing #111864 if he wants to do it another way. |
up to Sam of course, but perhaps invert it completely, and go with something like |
I commented on @hugovk's PR (#111864 (comment)). Macros like |
I put an issue in the steering council GitHub repo: python/steering-council#214 |
I propose "multicore". |
The SC decision: I've updated the PR. |
…dent. (#112300) Rename blurb snippet placed in the wrong directory by accident.
Rename Py_NOGIL to Py_GIL_DISABLED
…y accident. (python#112300) Rename blurb snippet placed in the wrong directory by accident.
From the PEP 703 acceptance:
Py_NOGIL
is a user-facing macro, let's rename it to something positive.Maybe
Py_DISABLE_GIL
orPy_FREE_THREADED
?cc @colesbury
Linked PRs
Py_NOGIL
toPy_GIL_DISABLED
#111864The text was updated successfully, but these errors were encountered: