Misspelled freethreading in 3.14.0b3

[hpkfft]

Bug report

Bug description:

Python 3.14.0b3 free-threading build (main, ....
>>> import sys
>> sys.version
'3.14.0b3 free-threading build (main, ....

@rgommers advised that https://github.com/python/steering-council/issues/221#issuecomment-1841593283 decision was freethreading should preferably not be hyphenated (if I understand correctly).

CPython versions tested on:

3.14

Operating systems tested on:

Linux

[hugovk]

"free-threaded build" is the correct spelling here: "free-threaded" is a compound adjective modifying the noun "build".

https://github.com/python/steering-council/issues/221#issuecomment-1841593283 is about what general term/name to use and when, rather than a decision on hyphenation.

Plus that freethreaded example is for package or installer names: we don't use code formatting for normal prose, which is the case here. (And I might argue should also contain a hyphen or underscore for accessibility, but that's not relevant here.)

[ZeroIntensity]

Yeah, I can't think of anything off the top of my head that uses "freethreading" over "free-threaded" or "free-threading". Even the topic label uses the hyphen!

[hpkfft]

I'm OK with any decision that is made; I just want my own documentation to be correct and professional.

If Python wants to declare that one should use freethreading as a single word, I'm fine with that.

The Chicago Manual of Style recommends that an "adjective + participle" should be hyphenated before but not after a noun and gives the following examples: "tight-lipped person", "high-jumping grasshoppers", "open-ended question", "the question was open ended"

So, I think, "free-threaded build" but "a build that is free threaded"

[kumaraditya303]

I think this is resolved now, closing.