From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Sun, 3 Mar 2024 19:56:50 +0000 (+0100) Subject: [3.12] gh-116010: Remove link to deprecated PEP 6 in FAQ guide (GH-116246) (#116286) X-Git-Tag: v3.12.3~160 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=722b9cf9fb9504bac082f474f0756da63a3674fc;p=thirdparty%2FPython%2Fcpython.git [3.12] gh-116010: Remove link to deprecated PEP 6 in FAQ guide (GH-116246) (#116286) Co-authored-by: Iman Tabrizian Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> --- diff --git a/Doc/faq/general.rst b/Doc/faq/general.rst index 8727332594bd..ec7c28975949 100644 --- a/Doc/faq/general.rst +++ b/Doc/faq/general.rst @@ -133,8 +133,6 @@ Python versions are numbered "A.B.C" or "A.B": changes. * *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 series of development releases are made, denoted as alpha, beta, or release 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 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 +`__ +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`.