[3.12] gh-116010: Remove link to deprecated PEP 6 in FAQ guide (GH-116246) (#116286)

Co-authored-by: Iman Tabrizian <iman.tabrizian@gmail.com>
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
This commit is contained in:
Miss Islington (bot) 2024-03-03 20:56:50 +01:00 committed by GitHub
parent e95e837541
commit 722b9cf9fb
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -133,8 +133,6 @@ Python versions are numbered "A.B.C" or "A.B":
changes. changes.
* *C* is the micro version number -- it is incremented for each bugfix release. * *C* is the micro version number -- it is incremented for each bugfix release.
See :pep:`6` for more information about bugfix releases.
Not all releases are bugfix releases. In the run-up to a new feature release, a Not all releases are bugfix releases. In the run-up to a new feature release, a
series of development releases are made, denoted as alpha, beta, or release series of development releases are made, denoted as alpha, beta, or release
candidate. Alphas are early releases in which interfaces aren't yet finalized; candidate. Alphas are early releases in which interfaces aren't yet finalized;
@ -157,7 +155,11 @@ unreleased versions, built directly from the CPython development repository. In
practice, after a final minor release is made, the version is incremented to the practice, after a final minor release is made, the version is incremented to the
next minor version, which becomes the "a0" version, e.g. "2.4a0". next minor version, which becomes the "a0" version, e.g. "2.4a0".
See also the documentation for :data:`sys.version`, :data:`sys.hexversion`, and See the `Developer's Guide
<https://devguide.python.org/developer-workflow/development-cycle/>`__
for more information about the development cycle, and
:pep:`387` to learn more about Python's backward compatibility policy. See also
the documentation for :data:`sys.version`, :data:`sys.hexversion`, and
:data:`sys.version_info`. :data:`sys.version_info`.