Fix broken links and update redirects

.github/CODE_OF_CONDUCT.md

@@ -4,7 +4,7 @@ Code of Conduct
 Please note that all interactions on
 [Python Software Foundation](https://www.python.org/psf-landing/)-supported
 infrastructure is [covered](https://www.python.org/psf/records/board/minutes/2014-01-06/#management-of-the-psfs-web-properties)
-by the [PSF Code of Conduct](https://www.python.org/psf/codeofconduct/),
+by the [PSF Code of Conduct](https://www.python.org/psf/conduct/),
 which includes all infrastructure used in the development of Python itself
 (e.g. mailing lists, issue trackers, GitHub, etc.).
 

.github/CONTRIBUTING.md

@@ -40,6 +40,6 @@ someone could take a look at your pull request.
 ## Code of Conduct
 
 All interactions for this project are covered by the
-[PSF Code of Conduct](https://www.python.org/psf/codeofconduct/). Everyone is
+[PSF Code of Conduct](https://www.python.org/psf/conduct/). Everyone is
 expected to be open, considerate, and respectful of others no matter their
 position within the project.

buildbots.rst

@@ -67,7 +67,7 @@ There are three ways of visualizing recent build results:
 
       bbreport.py -q 3.x
 
-* The buildbot "console" interface at http://buildbot.python.org/all/#/console
+* The buildbot "console" interface at https://buildbot.python.org/all/
   This works best on a wide, high resolution
   monitor.  Clicking on the colored circles will allow you to open a new page
   containing whatever information about that particular build is of interest to

buildworker.rst

@@ -19,12 +19,12 @@ to go about setting up a buildbot worker, getting it added, and some hints about
 buildbot maintenance.
 
 Anyone running a buildbot that is part of the fleet should subscribe to the
-`python-buildbots <https://mail.python.org/mailman/listinfo/python-buildbots>`_
+`python-buildbots <https://mail.python.org/mailman3/lists/python-buildbots.python.org/>`_
 mailing list.  This mailing list is also the place to contact if you want to
 contribute a buildbot but have questions.
 
 As for what kind of buildbot to run...take a look at our `current fleet
-<http://buildbot.python.org/all/#/workers>`_.  Pretty much anything that isn't
+<https://buildbot.python.org/all/>`_.  Pretty much anything that isn't
 on that list would be interesting: different Linux/UNIX distributions,
 different versions of the various OSes, other OSes if you or someone are
 prepared to make the test suite actually pass on that new OS.  Even if you only
@@ -185,7 +185,7 @@ To start the worker running for your initial testing, you can do::
 
 Then you can either wait for someone to make a commit, or you can pick a
 builder associated with your worker from the `list of builders
-<http://buildbot.python.org/all/#/builders>`_ and force a build.
+<https://buildbot.python.org/all/>`_ and force a build.
 
 In any case you should initially monitor builds on your builders to make sure
 the tests are passing and to resolve any platform issues that may be revealed
@@ -221,7 +221,7 @@ instance(s), so it is recommended to periodically check and make sure
 there are no "zombie" instances running on your account, created by the
 buildbot master.  Also, if you notice that your worker seems to have been
 down for an unexpectedly long time, please ping the `python-buildbots
-<https://mail.python.org/mailman/listinfo/python-buildbots>`_ list to
+<https://mail.python.org/mailman3/lists/python-buildbots.python.org/>`_ list to
 request that the master be restarted.
 
 Latent workers should also be updated periodically to include operating system

communication.rst

@@ -52,8 +52,8 @@ General Python questions should go to `python-list`_ or `tutor`_
 or similar resources, such as StackOverflow_ or the ``#python`` IRC channel
 on Libera.Chat_.
 
-`Core-Workflow <https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/>`_
-mailing list is the place to discuss and work on improvements to the CPython
+`The core-workflow <https://github.com/python/core-workflow/issues>`_
+issue tracker is the place to discuss and work on improvements to the CPython
 core development workflow.
 
 A complete list of Python mailing lists can be found at https://mail.python.org/mailman/listinfo.
@@ -65,10 +65,10 @@ RSS feed readers.
 .. _new-bugs-announce: https://mail.python.org/mailman/listinfo/new-bugs-announce
 .. _python-bugs-list: https://mail.python.org/mailman/listinfo/python-bugs-list
 .. _python-checkins: https://mail.python.org/mailman/listinfo/python-checkins
-.. _python-committers: https://mail.python.org/mailman/listinfo/python-committers
-.. _python-dev: https://mail.python.org/mailman/listinfo/python-dev
+.. _python-committers: https://mail.python.org/mailman3/lists/python-committers.python.org/
+.. _python-dev: https://mail.python.org/mailman3/lists/python-dev.python.org/
 .. _python-help: https://mail.python.org/mailman/listinfo/python-help
-.. _python-ideas: https://mail.python.org/mailman/listinfo/python-ideas
+.. _python-ideas: https://mail.python.org/mailman3/lists/python-ideas.python.org
 .. _python-list: https://mail.python.org/mailman/listinfo/python-list
 .. _tutor: https://mail.python.org/mailman/listinfo/tutor
 .. _StackOverflow: https://stackoverflow.com/
@@ -101,7 +101,7 @@ Blogs
 
 Several core developers are active bloggers and discuss Python's development
 that way. You can find their blogs (and various other developers who use Python)
-at http://planetpython.org/.
+at https://planetpython.org/.
 
 
 Standards of behaviour in these communication channels
@@ -119,7 +119,7 @@ Setting Expectations for Open Source Participation
 --------------------------------------------------
 
 Burn-out is common in open source due to a misunderstanding of what users, contributors,
-and maintainers should expect from each other. Brett Cannon gave a `talk <https://youtu.be/-Nk-8fSJM6I>`_
+and maintainers should expect from each other. Brett Cannon gave a `talk <https://www.youtube.com/watch?v=-Nk-8fSJM6I>`_
 about this topic that sets out to help everyone set reasonable expectations of each other in
 order to make open source pleasant for everyone involved.
 
@@ -133,6 +133,6 @@ Python `Performance Benchmark`_ project is intended to be an authoritative
 source of benchmarks for all Python implementations.
 
 .. _Python Core Workflow: https://github.com/python/core-workflow
-.. _cherry_picker: https://pypi.org/project/cherry-picker/
+.. _cherry_picker: https://pypi.org/project/cherry_picker/
 .. _blurb: https://pypi.org/project/blurb
 .. _Performance Benchmark: https://github.com/python/pyperformance

conf.py

@@ -227,6 +227,12 @@
     '\/.*',
 ]
 
+linkcheck_ignore = [
+    # The voters repo is private and appears as a 404
+    'https://github.com/python/voters/',
+    # The python-core team link is private, redirects to login
+    'https://github.com/orgs/python/teams/python-core',
+]
 
 # Use our custom CSS stylesheet to differentiate us from the official python
 # docs.

coredev.rst

@@ -63,7 +63,7 @@ Gaining Commit Privileges
 
 The steps to gaining commit privileges are:
 
-1. A core developer starts a poll at https://discuss.python.org/c/committers/
+1. A core developer starts a poll at https://discuss.python.org/c/committers/5
 
    - Open for 7 days
    - Results shown upon close
@@ -175,4 +175,4 @@ And finally, enjoy yourself! Contributing to open source software should be fun
 break or figure out what you need to do to make it enjoyable again.
 
 
-.. _PSF Code of Conduct: https://www.python.org/psf/codeofconduct/
+.. _PSF Code of Conduct: https://www.python.org/psf/conduct/

coverage.rst

@@ -112,7 +112,7 @@ If this does not work for you for some reason, you should try using the
 in-development version of coverage.py to see if it has been updated as needed.
 To do this you should clone/check out the development version of coverage.py:
 
-    git clone https://github.com/nedbat/coveragepy.git
+    git clone https://github.com/nedbat/coveragepy
 
 You will need to use the full path to the installation.
 

devcycle.rst

@@ -257,7 +257,7 @@ at all levels including organization membership, team membership, access
 control, and merge privileges on all repositories. For full details of the
 permission levels see `GitHub's documentation on Organization permission
 levels
-<https://help.github.com/articles/permission-levels-for-an-organization/#permission-levels-for-an-organization>`_.
+<https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#permissions-for-organization-roles>`_.
 This role is paramount to the security of the Python Language, Community, and
 Infrastructure.
 
@@ -300,8 +300,8 @@ Repository Administrator Role Policy
 The Administrator role on the repository allows for managing all aspects
 including collaborators, access control, integrations, webhooks, and branch
 protection. For full details of the permission levels see `GitHub's
-documentation on Repository permission levels
-<https://help.github.com/articles/repository-permission-levels-for-an-organization/>`_.
+documentation on repository permission levels
+<https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#permissions-for-organization-roles>`_.
 Common reasons for this role are: maintenance of Core Developer
 Workflow tooling, Release Managers for all :ref:`in-development <indevbranch>`,
 :ref:`maintenance <maintbranch>`, and :ref:`security mode <secbranch>`

docquality.rst

@@ -35,7 +35,7 @@ and :ref:`maintenance <maintbranch>` branches at https://docs.python.org/dev/.
 The in-development and recent maintenance branches are rebuilt once per day.
 
 If you would like to be more involved with documentation, consider subscribing
-to the `[email protected] <https://mail.python.org/mailman/listinfo/docs>`_
+to the `[email protected] <https://mail.python.org/mailman3/lists/docs.python.org/>`_
 mailing list. The `issue tracker`_ sends new documentation issues to this
 mailing list, and, less frequently, the list receives some directly mailed bug
 reports. The `[email protected] <https://mail.python.org/mailman/listinfo/doc-sig>`_
@@ -135,4 +135,4 @@ without errors.
 .. _separate repository:
 .. _devguide repo: https://github.com/python/devguide
 .. _devguide GitHub tracker: https://github.com/python/devguide/issues
-.. _Sphinx: http://www.sphinx-doc.org/
+.. _Sphinx: https://www.sphinx-doc.org/

documenting.rst

@@ -19,7 +19,7 @@ The documentation in HTML, PDF or EPUB format is generated from text files
 written using the :ref:`reStructuredText format <markup>` and contained in the
 :ref:`CPython Git repository <setup>`.
 
-.. _reStructuredText: http://docutils.sourceforge.net/rst.html
+.. _reStructuredText: https://docutils.sourceforge.io/rst.html
 
 .. note::
 
@@ -291,7 +291,7 @@ language, this will not take too long.
 .. seealso::
 
     The authoritative `reStructuredText User
-    Documentation <http://docutils.sourceforge.net/rst.html>`_.
+    Documentation <https://docutils.sourceforge.io/rst.html>`_.
 
 
 Paragraphs
@@ -537,7 +537,7 @@ they are used in the Python documentation.
 
    This is just an overview of Sphinx' extended markup capabilities; full
    coverage can be found in `its own documentation
-   <http://sphinx-doc.org/>`_.
+   <https://sphinx-doc.org/>`_.
 
 
 Meta-information markup
@@ -1649,7 +1649,7 @@ in production, other are work in progress:
 | Turkish (tr)    |                               | `GitHub <github_tr_>`_     |
 +-----------------+-------------------------------+----------------------------+
 
-.. _article_pt_br: http://rgth.co/blog/python-ptbr-cenario-atual
+.. _article_pt_br: https://rgth.co/blog/python-ptbr-cenario-atual/
 .. _bpo_cocoatomo: https://bugs.python.org/user19001
 .. _bpo_gbtami: https://bugs.python.org/user25857
 .. _bpo_kushal: https://bugs.python.org/user16382
@@ -1664,7 +1664,7 @@ in production, other are work in progress:
 .. _doc_pl: https://docs.python.org/pl/
 .. _doc_zh_cn: https://docs.python.org/zh-cn/
 .. _doc_zh_tw: https://docs.python.org/zh-tw/
-.. _github_ar: https://github.com/Abdur-rahmaanJ/py-docs-ar
+.. _github_ar: https://github.com/Abdur-rahmaanJ/python-docs-ar
 .. _github_bn_in: https://github.com/python/python-docs-bn-in
 .. _github_es: https://github.com/python/python-docs-es
 .. _github_fr: https://github.com/python/python-docs-fr
@@ -1685,7 +1685,7 @@ in production, other are work in progress:
 .. _tx_pl: https://www.transifex.com/python-doc/python-newest/
 .. _tx_zh_cn: https://www.transifex.com/python-doc/python-newest/
 .. _tx_zh_tw: https://www.transifex.com/python-tw-doc/python-36-tw
-.. _wiki_pt_br: http://python.org.br/traducao
+.. _wiki_pt_br: https://python.org.br/traducao/
 
 Starting a new translation
 --------------------------
@@ -1751,20 +1751,20 @@ Which version of Python documentation should be translated?
 
 Consensus is to work on current stable, you can then propagate your
 translation from a branch to another using `pomerge
-<https://pypi.org/p/pomerge>`__.
+<https://pypi.org/project/pomerge/>`__.
 
 
 Are there some tools to help in managing the repo?
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Here's what's we're using:
 
-- `pomerge <https://pypi.org/p/pomerge>`__ to propagate translation
+- `pomerge <https://pypi.org/project/pomerge/>`__ to propagate translation
   from a files to others.
-- `pospell <https://pypi.org/p/pospell>`__ to check for typo in po files.
-- `powrap <https://pypi.org/p/powrap>`__ to rewrap the ``.po`` files
+- `pospell <https://pypi.org/project/pospell/>`__ to check for typo in po files.
+- `powrap <https://pypi.org/project/powrap/>`__ to rewrap the ``.po`` files
   before committing, this helps keeping git diffs short.
-- `potodo <https://pypi.org/p/potodo>`__ to list what needs to be translated.
+- `potodo <https://pypi.org/project/potodo/>`__ to list what needs to be translated.
 
 
 
@@ -1819,8 +1819,8 @@ style.
 
 
 
-.. _docutils: http://docutils.sourceforge.net/
+.. _docutils: https://docutils.sourceforge.io/
 .. _python-docs-theme: https://pypi.org/project/python-docs-theme/
-.. _Sphinx: http://sphinx-doc.org/
+.. _Sphinx: https://sphinx-doc.org/
 .. _virtualenv: https://virtualenv.pypa.io/
 .. _blurb: https://pypi.org/project/blurb/

exploring.rst

@@ -83,7 +83,7 @@ building your understanding of both the 2.x and 3.x versions of CPython:
 
 .. _Yet another guided tour of CPython: https://paper.dropbox.com/doc/Yet-another-guided-tour-of-CPython-XY7KgFGn88zMNivGJ4Jzv
 
-.. _Python Asynchronous I/O Walkthrough: http://pgbovine.net/python-async-io-walkthrough.htm
+.. _Python Asynchronous I/O Walkthrough: https://www.youtube.com/playlist?list=PLpEcQSRWP2IjVRlTUptdD05kG-UkJynQThttps://www.youtube.com/playlist?list=PLpEcQSRWP2IjVRlTUptdD05kG-UkJynQT
 
 .. _Coding Patterns for Python Extensions: https://pythonextensionpatterns.readthedocs.io/en/latest/
 
@@ -95,4 +95,4 @@ building your understanding of both the 2.x and 3.x versions of CPython:
 
 .. _A guide from parser to objects, observed using Eclipse: https://docs.google.com/document/d/1nzNN1jeNCC_bg1LADCvtTuGKvcyMskV1w8Ad2iLlwoI/
 
-.. _CPython internals\: A ten-hour codewalk through the Python interpreter source code: http://pgbovine.net/cpython-internals.htm
+.. _CPython internals\: A ten-hour codewalk through the Python interpreter source code: https://www.youtube.com/playlist?list=PLzV58Zm8FuBL6OAv1Yu6AwXZrnsFbbR0S

gitbootcamp.rst

@@ -456,7 +456,7 @@ Pull requests can be accepted and merged by a Python Core Developer.
       * rebased
 
    .. note::
-      `How to Write a Git Commit Message <https://chris.beams.io/posts/git-commit/>`_
+      `How to Write a Git Commit Message <https://cbea.ms/git-commit/>`_
       is a nice article describing how to write a good commit message.
 
 4. Press the ``Confirm squash and merge`` button.

help.rst

@@ -34,8 +34,8 @@ of current Python design issues, release mechanics, and maintenance of
 existing releases.  These mailing lists are for questions involving the
 development *of* Python, **not** for development *with* Python.
 
-.. _python-ideas: https://mail.python.org/mailman/listinfo/python-ideas
-.. _python-dev: https://mail.python.org/mailman/listinfo/python-dev
+.. _python-ideas: https://mail.python.org/mailman3/lists/python-ideas.python.org
+.. _python-dev: https://mail.python.org/mailman3/lists/python-dev.python.org/
 
 Ask #python-dev
 ---------------

index.rst

@@ -238,14 +238,14 @@ Key Resources
     * :PEP:`7` (Style Guide for C Code)
     * :PEP:`8` (Style Guide for Python Code)
 * `Issue tracker`_
-    * `Meta tracker <http://psf.upfronthosting.co.za/roundup/meta>`_ (issue
+    * `Meta tracker <https://issues.roundup-tracker.org/>`_ (issue
       tracker for the issue tracker)
     * :doc:`experts`
 * `Buildbot status`_
 * Source code
     * `Browse online <https://github.com/python/cpython/>`_
     * `Snapshot of the *main* branch <https://github.com/python/cpython/archive/main.zip>`_
-    * `Daily OS X installer <http://buildbot.python.org/daily-dmg/>`_
+    * `Daily OS X installer <https://buildbot.python.org/daily-dmg/>`_
 * PEPs_ (Python Enhancement Proposals)
 * :doc:`help`
 * :doc:`developers`
@@ -281,7 +281,7 @@ Please note that all interactions on
 `Python Software Foundation <https://www.python.org/psf-landing/>`__-supported
 infrastructure is `covered
 <https://www.python.org/psf/records/board/minutes/2014-01-06/#management-of-the-psfs-web-properties>`__
-by the `PSF Code of Conduct <https://www.python.org/psf/codeofconduct/>`__,
+by the `PSF Code of Conduct <https://www.python.org/psf/conduct/>`__,
 which includes all infrastructure used in the development of Python itself
 (e.g. mailing lists, issue trackers, GitHub, etc.).
 In general this means everyone is expected to be open, considerate, and
@@ -337,9 +337,9 @@ Full Table of Contents
 .. _python.org maintenance: https://pythondotorg.readthedocs.io/
 .. _Python: https://www.python.org/
 .. _Core Python Mentorship: https://www.python.org/dev/core-mentorship/
-.. _PyPy: http://www.pypy.org
-.. _Jython: http://www.jython.org/
-.. _IronPython: http://ironpython.net/
-.. _Stackless: http://www.stackless.com/
+.. _PyPy: https://www.pypy.org
+.. _Jython: https://www.jython.org/
+.. _IronPython: https://ironpython.net/
+.. _Stackless: https://github.com/stackless-dev/stackless/wiki/
 .. _Issue tracker: https://bugs.python.org/
 .. _open pull requests: https://github.com/python/cpython/pulls?utf8=%E2%9C%93&q=is%3Apr%20is%3Aopen%20label%3A%22awaiting%20review%22

langchanges.rst

@@ -88,7 +88,7 @@ unconvinced. When there isn't an obvious victor then the
 For some examples on language changes that were accepted please read
 `Justifying Python Language Changes`_.
 
-.. _python-ideas: https://mail.python.org/mailman/listinfo/python-ideas
+.. _python-ideas: https://mail.python.org/mailman3/lists/python-ideas.python.org/
 .. _issue tracker: https://bugs.python.org
 .. _PEP Index: https://www.python.org/dev/peps/
 .. _draft PEP: https://www.python.org/dev/peps/pep-0001/