Disallow "No-GIL" from the glossary of specific words

[hugovk]

The Steering Council, on accepting PEP 703 (Making the Global Interpreter Lock Optional in CPython), said:

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?

[picnixz]

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.

[hugovk]

We don't, and we wouldn't want to fail on things like https://github.com/python/cpython/blob/bd3d31f380cd451a4ab6da5fbfde463fed95b5b5/Misc/NEWS.d/3.13.0a2.rst?plain=1#L1493

[picnixz]

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...)

[arunkumargururaj07-star]

Hi @hugovk! I would like to work on this.

To clarify the scope: I plan to update the Style Guide (likely glossary.rst or the specific style guide document) to explicitly recommend 'free-threaded' over 'No-GIL', citing the PEP 703 acceptance.

I will focus on the documentation update rather than creating an automated checking tool for now. Please assign this to me.

[StanFromIreland]

Hello, feel free to work on the issue, but we generally don't assign them here.