Merge remote-tracking branch 'upstream/main' into pep773

Author: zooba

.github/CODEOWNERS

@@ -149,7 +149,7 @@ peps/pep-0289.rst  @rhettinger
 peps/pep-0290.rst  @rhettinger
 # peps/pep-0291.rst
 peps/pep-0292.rst  @warsaw
-peps/pep-0293.rst  @doerwalter
+# peps/pep-0293.rst
 # peps/pep-0294.rst
 # peps/pep-0295.rst
 # peps/pep-0296.rst
@@ -262,16 +262,16 @@ peps/pep-0404.rst  @warsaw
 # peps/pep-0405.rst
 peps/pep-0406.rst  @ncoghlan
 peps/pep-0407.rst  @pitrou @birkenfeld @warsaw
-peps/pep-0408.rst  @ncoghlan @eliben
+peps/pep-0408.rst  @ncoghlan
 peps/pep-0409.rst  @ethanfurman
 peps/pep-0410.rst  @vstinner
-peps/pep-0411.rst  @ncoghlan @eliben
+peps/pep-0411.rst  @ncoghlan
 peps/pep-0412.rst  @markshannon
 peps/pep-0413.rst  @ncoghlan
 peps/pep-0414.rst  @mitsuhiko @ncoghlan
 peps/pep-0415.rst  @benjaminp
 peps/pep-0416.rst  @vstinner
-peps/pep-0417.rst  @voidspace
+# peps/pep-0417.rst
 peps/pep-0418.rst  @vstinner
 peps/pep-0418/     @vstinner
 # peps/pep-0419.rst
@@ -292,7 +292,7 @@ peps/pep-0432.rst  @ncoghlan @vstinner @ericsnowcurrently
 peps/pep-0433.rst  @vstinner
 peps/pep-0433/     @vstinner
 peps/pep-0434.rst  @terryjreedy
-peps/pep-0435.rst  @warsaw @eliben @ethanfurman
+peps/pep-0435.rst  @warsaw @ethanfurman
 peps/pep-0436.rst  @larryhastings
 # peps/pep-0437.rst
 # peps/pep-0438.rst
@@ -650,8 +650,10 @@ peps/pep-0768.rst  @pablogsal
 peps/pep-0769.rst  @facundobatista
 peps/pep-0770.rst  @sethmlarson @brettcannon
 peps/pep-0771.rst  @pradyunsg
+peps/pep-0772.rst  @warsaw @pradyunsg
 peps/pep-0773.rst  @zooba
 peps/pep-0774.rst  @savannahostrowski
+peps/pep-0775.rst  @encukou
 # ...
 peps/pep-0777.rst  @warsaw
 # ...

pep_sphinx_extensions/pep_processor/parsing/pep_banner_directive.py

@@ -6,7 +6,7 @@
 from docutils.parsers import rst
 
 PYPA_SPEC_BASE_URL = "https://packaging.python.org/en/latest/specifications/"
-TYPING_SPEC_BASE_URL = "https://typing.readthedocs.io/en/latest/spec/"
+TYPING_SPEC_BASE_URL = "https://typing.python.org/en/latest/spec/"
 
 
 class PEPBanner(rst.Directive):
@@ -113,7 +113,7 @@ class CanonicalTypingSpecBanner(PEPBanner):
     admonition_pre_text = admonition_pre_template
     admonition_post_text = (
         "See the `typing specification update process "
-        "<https://typing.readthedocs.io/en/latest/spec/meta.html>`__ "
+        "<https://typing.python.org/en/latest/spec/meta.html>`__ "
         "for how to propose changes to the typing spec."
     )
     css_classes = ["canonical-typing-spec", "sticky-banner"]

peps/conf.py

@@ -75,7 +75,7 @@
     "py3.14": ("https://docs.python.org/3.14/", None),
     "python": ("https://docs.python.org/3/", None),
     "trio": ("https://trio.readthedocs.io/en/latest/", None),
-    "typing": ("https://typing.readthedocs.io/en/latest/", None),
+    "typing": ("https://typing.python.org/en/latest/", None),
 }
 intersphinx_disabled_reftypes = []
 

peps/pep-0012.rst

@@ -656,7 +656,7 @@ You can use
 to other Sphinx sites,
 such as the `Python documentation <https://docs.python.org/>`_
 `packaging.python.org <https://packaging.python.org/>`_,
-and `typing.readthedocs.io <https://typing.readthedocs.io/>`_,
+and `typing.python.org <https://typing.python.org/>`_,
 to easily cross-reference pages, sections and Python/C objects.
 
 For example,

peps/pep-0387.rst

@@ -199,6 +199,7 @@ several releases:
 Changelog
 =========
 
+* 2025-Jan-27: Updated to prefer a 5-year deprecation period before removal.
 * 2023-Nov-14: Added ``@deprecated`` decorator per :pep:`702`.
 * 2023-Jul-03: Added the Soft Deprecation section, as discussed in
   `<https://discuss.python.org/t/27957>`__.

peps/pep-0508.rst

@@ -10,6 +10,8 @@ Created: 11-Nov-2015
 Post-History: 05-Nov-2015, 16-Nov-2015
 Resolution: https://mail.python.org/pipermail/distutils-sig/2015-November/027868.html
 
+.. canonical-pypa-spec:: :ref:`packaging:dependency-specifiers`
+
 
 Abstract
 ========

peps/pep-0545.rst

@@ -20,10 +20,10 @@ to attract and motivate new translators and new translations.
 Translated documentation will be hosted on python.org.  Examples of
 two active translation teams:
 
-* http://docs.python.org/fr/: French
-* http://docs.python.org/ja/: Japanese
+* https://docs.python.org/fr/: French
+* https://docs.python.org/ja/: Japanese
 
-http://docs.python.org/en/ will redirect to http://docs.python.org/.
+https://docs.python.org/en/ will redirect to https://docs.python.org/.
 
 Sources of translated documentation will be hosted in the Python
 organization on GitHub: https://github.com/python/.  Contributors will
@@ -77,22 +77,22 @@ Issue tracker
 
 Considering that issues opened about translations may be written in
 the translation language, which can be considered noise but at least
-is inconsistent, issues should be placed outside `bugs.python.org
-<https://bugs.python.org/>`_ (b.p.o).
+is inconsistent, issues should not be placed in the `CPython issue tracker
+<https://github.com/python/cpython/issues/>`_.
 
 As all translation must have their own GitHub project (see `Repository
 for Po Files`_), they must use the associated GitHub issue tracker.
 
 Considering the noise induced by translation issues redacted in any
-languages which may beyond every warnings land in b.p.o, triage will
+languages which may beyond every warnings land in the issue tracker, triage will
 have to be done.  Considering that translations already exist and are
-not actually a source of noise in b.p.o, an unmanageable amount of
+not actually a source of noise in issue tracker, an unmanageable amount of
 work is not to be expected.  Considering that Xiang Zhang and Victor
 Stinner are already triaging, and Julien Palard is willing to help on
-this task, noise on b.p.o is not to be expected.
+this task, noise on issue tracker is not to be expected.
 
 Also, language team coordinators (see `Language Team`_) should help
-with triaging b.p.o by properly indicating, in the language of the
+with triaging the issue tracker by properly indicating, in the language of the
 issue author if required, the right issue tracker.
 
 
@@ -106,10 +106,10 @@ done in one branch to other branches.
 .. note::
    Translation memories are a kind of database of previously translated
    paragraphs, even removed ones.  See also `Sphinx Internationalization
-   <http://www.sphinx-doc.org/en/stable/intl.html>`_.
+   <https://www.sphinx-doc.org/en/stable/intl.html>`_.
 
-The three currently stable branches that will be translated are [12]_:
-2.7, 3.5, and 3.6.  The scripts to build the documentation of older
+The newest currently stable branch will be translated and translations
+can be propagated to other branches. The scripts to build the documentation of older
 branches needs to be modified to support translation [12]_, whereas
 these branches now only accept security-only fixes.
 
@@ -319,6 +319,14 @@ Other tools may be used later like https://pontoon.mozilla.org/
 and http://zanata.org/.
 
 
+python-docs-translations
+''''''''''''''''''''''''
+
+The `python-docs-translations GitHub organization <https://github.com/python-docs-translations>`_
+is home to several useful translation tools such as the translations
+`dashboard <https://github.com/python-docs-translations/dashboard>`_.
+
+
 Documentation Contribution Agreement
 ''''''''''''''''''''''''''''''''''''
 
@@ -363,7 +371,7 @@ Each language team should have one coordinator responsible for:
 - Ensure contributors understand and agree with the documentation
   contribution agreement.
 - Ensure quality (grammar, vocabulary, consistency, filtering spam, ads, …).
-- Redirect issues posted on b.p.o to the correct GitHub issue tracker
+- Redirect issues posted on issue tracker to the correct GitHub issue tracker
   for the language.
 
 
@@ -606,10 +614,10 @@ References
    (https://git.afpy.org/AFPy/python-docs-fr)
 
 .. [18] French mailing list
-   (http://lists.afpy.org/mailman/listinfo/traductions)
+   (https://lists.afpy.org/mailman/listinfo/traductions)
 
 .. [19] Japanese translation
-   (http://docs.python.jp/3/)
+   (https://docs.python.jp/3/)
 
 .. [20] Japanese translation on GitHub
    (https://github.com/python-doc-ja/python-doc-ja)
@@ -627,10 +635,10 @@ References
    (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Language)
 
 .. [25] Документация Python 2.7!
-   (http://python-lab.ru/documentation/index.html)
+   (https://python-lab.ru/documentation/index.html)
 
 .. [26] Python-oktató
-   (http://web.archive.org/web/20170526080729/http://harp.pythonanywhere.com/python_doc/tutorial/index.html)
+   (https://web.archive.org/web/20170526080729/http://harp.pythonanywhere.com/python_doc/tutorial/index.html)
 
 .. [27] The Python-hu Archives
    (https://mail.python.org/pipermail/python-hu/)

peps/pep-0688.rst

@@ -349,7 +349,7 @@ How to Teach This
 =================
 
 We will add notes pointing to ``collections.abc.Buffer`` in appropriate places in the
-documentation, such as `typing.readthedocs.io <https://typing.readthedocs.io/en/latest/>`__
+documentation, such as `typing.python.org <https://typing.python.org/en/latest/>`__
 and the `mypy cheat sheet <https://mypy.readthedocs.io/en/stable/cheat_sheet_py3.html>`__.
 Type checkers may provide additional pointers in their error messages. For example,
 when they encounter a buffer object being passed to a function that

peps/pep-0692.rst

@@ -457,7 +457,7 @@ This PEP could be linked in the ``typing`` module's documentation. Moreover, a
 new section on using ``Unpack`` could be added to the aforementioned docs.
 Similar sections could be also added to the
 `mypy documentation <https://mypy.readthedocs.io/>`_ and the
-`typing RTD documentation <https://typing.readthedocs.io/>`_.
+`typing documentation <https://typing.python.org/>`_.
 
 Reference Implementation
 ========================

peps/pep-0693.rst

@@ -65,10 +65,10 @@ Actual:
 - 3.12.6: Friday, 2024-09-06
 - 3.12.7: Tuesday, 2024-10-01
 - 3.12.8: Tuesday, 2024-12-03
+- 3.12.9: Tuesday, 2025-02-04
 
 Expected:
 
-- 3.12.9: Tuesday, 2025-02-04
 - 3.12.10: Tuesday, 2025-04-08
 
 Source-only security fix releases
@@ -81,7 +81,7 @@ Provided irregularly on an as-needed basis until October 2028.
 
 3.12 will receive bugfix updates approximately every 2 months for
 approximately 18 months.  Some time after the release of 3.13.0 final,
-the ninth and final 3.12 bugfix update will be released.  After that,
+the tenth and final 3.12 bugfix update will be released.  After that,
 it is expected that security updates (source only) will be released
 until 5 years after the release of 3.12.0 final, so until approximately
 October 2028.