Fix broken links

Author: dukecat0

README.rst

@@ -7,7 +7,7 @@ The "Python Packaging User Guide" (PyPUG) aims to be the authoritative resource
 how to package and install distributions in Python using current tools.
 
 To follow the development of Python packaging, see the `Python
-Packaging Authority <https://www.pypa.io>`_.
+Packaging Authority <https://www.pypa.io/en/latest/>`_.
 
 Code of Conduct
 ---------------

source/conf.py

@@ -383,6 +383,13 @@
 
 linkcheck_ignore = [
     "http://localhost:\d+",
+    # Ignoring these links as they will redirect to login page if folks haven't logged in.
+    "https://github.com/pypa/packaging-problems/issues/new?template=general_issue.yml",
+    "https://github.com/pypa/packaging-problems/issues/new?template=packaging_tutorial.yml&title=Trouble+with+the+packaging+tutorial&guide=https://packaging.python.org/tutorials/packaging-projects",
+    # This shows that PyPI previously hosted at pypi.python.org
+    "https://pypi.python.org",
+    # Weblate has different UI for different languages
+    "https://weblate.org/",
 ]
 
 # Example configuration for intersphinx: refer to the Python standard library.

source/contribute.rst

@@ -18,9 +18,9 @@ Most of the work on the |PyPUG| takes place on the
 `open issues`__ and `pull requests`__. If you're planning to write or edit
 the guide, please read the :ref:`style guide <contributing_style_guide>`.
 
-.. __: https://github.com/pypa/python-packaging-user-guide/
-.. __: https://github.com/pypa/python-packaging-user-guide/issues
-.. __: https://github.com/pypa/python-packaging-user-guide/pulls
+.. __: https://github.com/pypa/packaging.python.org/
+.. __: https://github.com/pypa/packaging.python.org/issues
+.. __: https://github.com/pypa/packaging.python.org/pulls
 
 By contributing to the |PyPUG|, you're expected to follow the PSF's
 `Code of Conduct`__.
@@ -124,7 +124,7 @@ Though not required to contribute, it may be useful to build this guide locally
 in order to test your changes. In order to build this guide locally, you'll
 need:
 
-1. `Nox <https://nox.readthedocs.io/en/latest/>`_. You can install or upgrade
+1. `Nox <https://nox.thea.codes/en/latest/>`_. You can install or upgrade
    nox using ``pip``:
 
    .. code-block:: bash
@@ -136,7 +136,7 @@ need:
    Python 3.6 on your operating system.
 
 .. _Hitchhiker's Guide to Python installation instructions:
-    http://docs.python-guide.org/en/latest/starting/installation/
+    https://docs.python-guide.org/starting/installation/
 
 To build the guide, run the following bash command in the source folder:
 

source/discussions/deploying-python-applications.rst

@@ -73,7 +73,7 @@ directory, independent of any other Python installation on the computer.
 
 A big advantage of Pynsist is that the Windows packages can be built on Linux.
 There are several examples for different kinds of programs (console, GUI) in
-the `documentation <https://pynsist.readthedocs.io>`__. The tool is released
+the `documentation <https://pynsist.readthedocs.io/en/latest/>`__. The tool is released
 under the MIT-licence.
 
 Application bundles

source/discussions/install-requires-vs-requirements.rst

@@ -88,4 +88,4 @@ installs them using ``python -m pip install -r``.
 ----
 
 .. [1] For more on "Abstract" vs "Concrete" requirements, see
-       https://caremad.io/2013/07/setup-vs-requirement/.
+       https://caremad.io/posts/2013/07/setup-vs-requirement/.

source/discussions/wheel-vs-egg.rst

@@ -39,7 +39,7 @@ Here's a breakdown of the important differences between :term:`Wheel` and :term:
   specification and the implementation that packaged it.
 
 * :term:`Wheel` is internally organized by `sysconfig path type
-  <http://docs.python.org/2/library/sysconfig.html#installation-paths>`_,
+  <https://docs.python.org/2/library/sysconfig.html#installation-paths>`_,
   therefore making it easier to convert to other formats.
 
 ----

source/glossary.rst

@@ -128,12 +128,12 @@ Glossary
 
         PyPA is a working group that maintains many of the relevant
         projects in Python packaging. They maintain a site at
-        https://www.pypa.io, host projects on `GitHub
+        https://www.pypa.io/en/latest/, host projects on `GitHub
         <https://github.com/pypa>`_ and `Bitbucket
         <https://bitbucket.org/pypa>`_, and discuss issues on the
         `distutils-sig mailing list
         <https://mail.python.org/mailman3/lists/distutils-sig.python.org/>`_
-	and `the Python Discourse forum <https://discuss.python.org/c/packaging>`__.
+	and `the Python Discourse forum <https://discuss.python.org/c/packaging/14>`__.
 
 
     Python Package Index (PyPI)

source/guides/analyzing-pypi-package-downloads.rst

@@ -83,7 +83,7 @@ include:
 +------------------------+-----------------+-----------------------------+
 | file.version           | Package version | ``0.1.6``, ``1.4.2``        |
 +------------------------+-----------------+-----------------------------+
-| details.installer.name | Installer       | pip, `bandersnatch`_        |
+| details.installer.name | Installer       | pip, :ref:`bandersnatch`    |
 +------------------------+-----------------+-----------------------------+
 | details.python         | Python version  | ``2.7.12``, ``3.6.4``       |
 +------------------------+-----------------+-----------------------------+
@@ -304,7 +304,6 @@ References
 .. [#] `PyPI BigQuery dataset announcement email <https://mail.python.org/pipermail/distutils-sig/2016-May/028986.html>`__
 
 .. _public PyPI download statistics dataset: https://console.cloud.google.com/bigquery?p=bigquery-public-data&d=pypi&page=dataset
-.. _bandersnatch: /key_projects/#bandersnatch
 .. _Google BigQuery: https://cloud.google.com/bigquery
 .. _BigQuery web UI: https://console.cloud.google.com/bigquery
 .. _pypinfo: https://github.com/ofek/pypinfo/blob/master/README.rst

source/guides/creating-and-discovering-plugins.rst

@@ -171,5 +171,5 @@ Now the module of your choice can be imported by executing
    <python:library/importlib.metadata>`, most packaging tools other than setuptools
    provide support for defining entry points.
 
-.. _Setuptools: https://setuptools.readthedocs.io
+.. _Setuptools: https://setuptools.readthedocs.io/en/latest/
 .. _backport: https://importlib-metadata.readthedocs.io/en/latest/

source/guides/distributing-packages-using-setuptools.rst

@@ -57,7 +57,7 @@ setup.py
 
 The most important file is :file:`setup.py` which exists at the root of your
 project directory. For an example, see the `setup.py
-<https://github.com/pypa/sampleproject/blob/master/setup.py>`_ in the `PyPA
+<https://github.com/pypa/sampleproject/blob/main/setup.py>`_ in the `PyPA
 sample project <https://github.com/pypa/sampleproject>`_.
 
 :file:`setup.py` serves two primary functions:
@@ -78,7 +78,7 @@ setup.cfg
 
 :file:`setup.cfg` is an ini file that contains option defaults for
 :file:`setup.py` commands.  For an example, see the `setup.cfg
-<https://github.com/pypa/sampleproject/blob/master/setup.cfg>`_ in the `PyPA
+<https://github.com/pypa/sampleproject/blob/main/setup.cfg>`_ in the `PyPA
 sample project <https://github.com/pypa/sampleproject>`_.
 
 
@@ -87,13 +87,13 @@ README.rst / README.md
 
 All projects should contain a readme file that covers the goal of the project.
 The most common format is `reStructuredText
-<http://docutils.sourceforge.net/rst.html>`_ with an "rst" extension, although
+<https://docutils.sourceforge.io/rst.html>`_ with an "rst" extension, although
 this is not a requirement; multiple variants of `Markdown
 <https://daringfireball.net/projects/markdown/>`_ are supported as well (look
 at ``setup()``'s :ref:`long_description_content_type <description>` argument).
 
 For an example, see `README.md
-<https://github.com/pypa/sampleproject/blob/master/README.md>`_ from the `PyPA
+<https://github.com/pypa/sampleproject/blob/main/README.md>`_ from the `PyPA
 sample project <https://github.com/pypa/sampleproject>`_.
 
 .. note:: Projects using :ref:`setuptools` 0.6.27+ have standard readme files
@@ -113,7 +113,7 @@ writing a :file:`MANIFEST.in` file, including a list of what's included by
 default, see ":ref:`Using MANIFEST.in`".
 
 For an example, see the `MANIFEST.in
-<https://github.com/pypa/sampleproject/blob/master/MANIFEST.in>`_ from the `PyPA
+<https://github.com/pypa/sampleproject/blob/main/MANIFEST.in>`_ from the `PyPA
 sample project <https://github.com/pypa/sampleproject>`_.
 
 .. note:: :file:`MANIFEST.in` does not affect binary distributions such as wheels.
@@ -128,7 +128,7 @@ If you're unsure which license to choose, you can use resources such as
 `GitHub's Choose a License <https://choosealicense.com/>`_ or consult a lawyer.
 
 For an example, see the `LICENSE.txt
-<https://github.com/pypa/sampleproject/blob/master/LICENSE.txt>`_ from the `PyPA
+<https://github.com/pypa/sampleproject/blob/main/LICENSE.txt>`_ from the `PyPA
 sample project <https://github.com/pypa/sampleproject>`_.
 
 <your package>
@@ -139,7 +139,7 @@ Python modules and packages under a single top-level package that has the same
 :ref:`name <setup() name>` as your project, or something very close.
 
 For an example, see the `sample
-<https://github.com/pypa/sampleproject/tree/master/src/sample>`_ package that's
+<https://github.com/pypa/sampleproject/tree/main/src/sample>`_ package that's
 included in the `PyPA sample project <https://github.com/pypa/sampleproject>`_.
 
 
@@ -154,7 +154,7 @@ specific details of your project are defined.
 
 The most relevant arguments are explained below. Most of the snippets given are
 taken from the `setup.py
-<https://github.com/pypa/sampleproject/blob/master/setup.py>`_ contained in the
+<https://github.com/pypa/sampleproject/blob/main/setup.py>`_ contained in the
 `PyPA sample project <https://github.com/pypa/sampleproject>`_.
 
 
@@ -237,7 +237,7 @@ A `content type
 can be specified with the ``long_description_content_type`` argument, which can
 be one of ``text/plain``, ``text/x-rst``, or ``text/markdown``, corresponding
 to no formatting, `reStructuredText (reST)
-<http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#reference-names>`_,
+<https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html#reference-names>`_,
 and the Github-flavored Markdown dialect of `Markdown
 <https://daringfireball.net/projects/markdown/>`_ respectively.
 
@@ -477,7 +477,7 @@ Each file name in ``files`` is interpreted relative to the :file:`setup.py`
 script at the top of the project source distribution.
 
 For more information see the distutils section on `Installing Additional Files
-<http://docs.python.org/3/distutils/setupscript.html#installing-additional-files>`_.
+<https://docs.python.org/3/distutils/setupscript.html#installing-additional-files>`_.
 
 .. note::
 
@@ -491,7 +491,7 @@ For more information see the distutils section on `Installing Additional Files
 ~~~~~~~~~~~
 
 Although ``setup()`` supports a `scripts
-<http://docs.python.org/3/distutils/setupscript.html#installing-scripts>`_
+<https://docs.python.org/3/distutils/setupscript.html#installing-scripts>`_
 keyword for pointing to pre-made scripts to install, the recommended approach to
 achieve cross-platform compatibility is to use :ref:`console_scripts` entry
 points (see below).
@@ -576,7 +576,7 @@ Semantic versioning (preferred)
 *******************************
 
 For new projects, the recommended versioning scheme is based on `Semantic Versioning
-<http://semver.org>`_, but adopts a different approach to handling pre-releases and
+<https://semver.org/>`_, but adopts a different approach to handling pre-releases and
 build metadata.
 
 The essence of semantic versioning is a 3-part MAJOR.MINOR.MAINTENANCE numbering scheme,
@@ -592,7 +592,7 @@ Adopting this approach as a project author allows users to make use of :pep:`"co
 a matching MAJOR version.
 
 Python projects adopting semantic versioning should abide by clauses 1-8 of the
-`Semantic Versioning 2.0.0 specification <http://semver.org>`_.
+`Semantic Versioning 2.0.0 specification <https://semver.org/>`_.
 
 Date based versioning
 *********************