It's final in the sense there will be no other 3.11.0 version.
If you want to be pedantic, 3.11.0 stable would also be a bad name - what if it's not actually stable but crashes all the time?
And 3.11.0 actual, what does it actually mean? Is there a non-actual 3.11.0?
Re:Python 3.11.0 final is now available
by quietbritishjim on Tuesday October 25, 2022 @09:57AM
(#33330519)
Does the first need a special name at all? The .0 (without b or rc, etc.) communicates its meaning just fine.
Re:Python 3.11.0 final is now available
by willsmith72 on Tuesday October 25, 2022 @10:11AM
(#33330682)
Maybe we can change "final" to "finally"
Re:Python 3.11.0 final is now available
by pistolpeteDK on Tuesday October 25, 2022 @11:11AM
(#33331651)
I agree.
Maybe "3.11.0 public" or "3.11.0 release" would be better suited to distinguish between the various dev-builds and the "final" release of the minor version
Re:Python 3.11.0 final is now available
by AdrianoKF on Tuesday October 25, 2022 @11:51AM
(#33332242)
Not that it takes away from any confusion that arises from the wording, but (at least) it is consistent with the definitions from PEP 440:
> A version identifier that consists solely of a release segment and optionally an epoch identifier is termed a “final release”.
I get it, 3.11.0 is "final" in the sense of "definitive" from the development team's point of view, the final one of the pre-releases. But 3.11.9 is also called "the ninth and final 3.11 bugfix update" in the schedule [1], the actual final one from the maintenance team's point of view, in the sense there will be no more.
Can't we find better terms, that work for everyone? 3.11.0 stable? 3.11.0 actual? For anyone but the dev team, this is in no way a "final" release, this is the "first" release.
[1]: https://peps.python.org/pep-0664/#lifespan