You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to avoid negatives in terms and flags and such, so we won’t get into double-negative terrain (like we do when we talk about ‘non no-GIL’). We’d like a positive, clear term to talk about the no-GIL build, and we’re suggesting ‘free-threaded’. (Relatedly, that’s why the build mode/ABI letter is ‘t’ and not ‘n’; that change was already made.)
"No-GIL" comes up regularly; shall we add this to the style guide so we have something to point to beyond the lengthy acceptance message?
The text was updated successfully, but these errors were encountered:
By the way, do we have a tool checking for such strings actually? because we could run a simple grep on the files as a GH action so that it's automatic.
You could have a tool in Python with an ignore file including the lines to ignore (having a tool could help people that do not know about bad words but I don't know how much of ignored lines we will need to have...)
The Steering Council, on accepting PEP 703 (Making the Global Interpreter Lock Optional in CPython), said:
"No-GIL" comes up regularly; shall we add this to the style guide so we have something to point to beyond the lengthy acceptance message?
The text was updated successfully, but these errors were encountered: