Use intersphinx references

Author: dukecat0

source/conf.py

@@ -398,10 +398,22 @@
 
 # Example configuration for intersphinx: refer to the Python standard library.
 intersphinx_mapping = {
+    'build': ('https://pypa-build.readthedocs.io/en/stable/', None),
+    'boltons': ('https://boltons.readthedocs.io/en/latest/', None),
+    'cffi': ('https://cffi.readthedocs.io/en/latest/', None),
+    'conda': ('https://conda.io/en/latest/', None),
+    'distlib': ('https://distlib.readthedocs.io/en/latest/', None),
+    'devpi': ('https://devpi.net/docs/devpi/devpi/latest/+doc', None),
+    'dh-virtualenv': ('https://dh-virtualenv.readthedocs.io/en/latest/', None),
+    'flexx': ('https://flexx.readthedocs.io/en/latest/', None),
     'openstack': ('https://docs.openstack.org/glance/latest/', None),
+    'packaging': ('https://packaging.pypa.io/en/latest/', None),
+    'packaging.python.org': ('https://packaging.python.org/', None),
+    'piwheels': ('https://piwheels.readthedocs.io/en/latest/', None),
     'python': ('https://docs.python.org/3', None),
     'python2': ('https://docs.python.org/2', None),
     'pip': ('https://pip.pypa.io/en/latest/', None),
+    'pipenv': ('https://pipenv.pypa.io/en/latest/', None),
     'scipy': ('https://www.scipy.org', None),
     'setuptools': ('https://setuptools.readthedocs.io/en/latest/', None),
     'tox': ('https://tox.readthedocs.io/en/latest/', None),
@@ -410,11 +422,11 @@
     'nox': ('https://nox.thea.codes/en/latest/', None),
     'pynsist': ('https://pynsist.readthedocs.io/en/latest/', None),
     'scipy': ('https://www.scipy.org', None),
+    'spack': ('https://spack.readthedocs.io/en/latest/', None),
     'sphinx': ('https://www.sphinx-doc.org/en/master', None),
     'pybind11': ('https://pybind11.readthedocs.io/en/stable/', None),
-    'cffi': ('https://cffi.readthedocs.io/en/latest/', None),
     'python-guide': ('https://docs.python-guide.org', None),
-    
+    'virtualenv': ('https://virtualenv.pypa.io/en/stable/', None),
 }
 
 

source/glossary.rst

@@ -128,7 +128,7 @@ 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/en/latest/, host projects on `GitHub
+        :doc:`pypa.io <pypa:index>`, host projects on `GitHub
         <https://github.com/pypa>`_ and `Bitbucket
         <https://bitbucket.org/pypa>`_, and discuss issues on the
         `distutils-sig mailing list

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

@@ -120,7 +120,7 @@ a list of packages to :func:`setup`'s ``packages`` argument instead of using
 Using package metadata
 ======================
 
-`Setuptools`_ provides :doc:`special support
+:doc:`Setuptools <setuptools:index>` provides :doc:`special support
 <setuptools:userguide/entry_point>` for plugins. By providing the
 ``entry_points`` argument to :func:`setup` in :file:`setup.py` plugins can
 register themselves for discovery.
@@ -171,5 +171,4 @@ 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/en/latest/
 .. _backport: https://importlib-metadata.readthedocs.io/en/latest/

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

@@ -476,8 +476,8 @@ and it is interpreted relative to the installation prefix
 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
-<https://docs.python.org/3/distutils/setupscript.html#installing-additional-files>`_.
+For more information see the distutils section on :ref:`Installing Additional Files
+<python:distutils-additional-files>`.
 
 .. note::
 
@@ -490,8 +490,8 @@ For more information see the distutils section on `Installing Additional Files
 ``scripts``
 ~~~~~~~~~~~
 
-Although ``setup()`` supports a `scripts
-<https://docs.python.org/3/distutils/setupscript.html#installing-scripts>`_
+Although ``setup()`` supports a :ref:`scripts
+<python:distutils-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).

source/guides/hosting-your-own-index.rst

@@ -6,7 +6,7 @@ Hosting your own simple repository
 
 
 If you wish to host your own simple repository [1]_, you can either use a
-software package like `devpi`_ or you can use simply create the proper
+software package like :doc:`devpi <devpi:index>` or you can use simply create the proper
 directory structure and use any web server that can serve static files and
 generate an autoindex.
 
@@ -59,5 +59,4 @@ instruct users to add the URL to their installer's configuration.
        :pep:`503`.
 
 
-.. _devpi: https://devpi.net/docs/devpi/devpi/latest/%2Bd/index.html
 .. _Twisted: https://twistedmatrix.com/trac/

source/guides/installing-scientific-packages.rst

@@ -98,8 +98,8 @@ install the :ref:`scientific Python stack
 SciPy distributions
 -------------------
 
-The SciPy site lists `several distributions
-<https://www.scipy.org/install.html>`__ that provide the full SciPy stack to
+The SciPy site lists :doc:`several distributions
+<scipy:install>` that provide the full SciPy stack to
 end users in an easy to use and update format.
 
 Some of these distributions may not be compatible with the standard ``pip``

source/guides/making-a-pypi-friendly-readme.rst

@@ -97,7 +97,7 @@ If your README is written in reStructuredText, any invalid markup will prevent
 it from rendering, causing PyPI to instead just show the README's raw source.
 
 Note that Sphinx extensions used in docstrings, such as
-`directives and roles <https://www.sphinx-doc.org/en/master/usage/restructuredtext/index.html>`_ 
+:doc:`directives and roles <sphinx:usage/restructuredtext/index>`
 (e.g., "``:py:func:`getattr```" or "``:ref:`my-reference-label```"), are not allowed here and will result in error
 messages like "``Error: Unknown interpreted text role "py:func".``".
 

source/guides/packaging-binary-extensions.rst

@@ -165,14 +165,14 @@ wrapper modules up to date.
   hand, however, and is very repetitive, so may not be a good choice for
   wrapping large APIs.
 
-* `pybind11 <https://pybind11.readthedocs.io/en/stable/>`__ is a pure C++11 library
+* :doc:`pybind11 <pybind11:index>` is a pure C++11 library
   that provides a clean C++ interface to the CPython (and PyPy) C API. It
   does not require a pre-processing step; it is written entirely in
   templated C++. Helpers are included for Setuptools or CMake builds. It
   was based on `Boost.Python <https://www.boost.org/doc/libs/1_76_0/libs/python/doc/html/index.html>`__,
   but doesn't require the Boost libraries or BJam.
 
-* `cffi <https://cffi.readthedocs.io/en/latest/>`__ is a project created by some of the PyPy
+* :doc:`cffi <cffi:index>` is a project created by some of the PyPy
   developers to make it straightforward for developers that already know
   both Python and C to expose their C modules to Python applications. It
   also makes it relatively straightforward to wrap a C module based on its

source/guides/packaging-namespace-packages.rst

@@ -169,7 +169,7 @@ in the `pkgutil namespace example project`_.
 pkg_resources-style namespace packages
 --------------------------------------
 
-`Setuptools`_ provides the `pkg_resources.declare_namespace`_ function and
+:doc:`Setuptools <setuptools:index>` provides the `pkg_resources.declare_namespace`_ function and
 the ``namespace_packages`` argument to :func:`~setuptools.setup`. Together
 these can be used to declare namespace packages. While this approach is no
 longer recommended, it is widely present in most existing namespace packages.
@@ -236,7 +236,6 @@ to :func:`~setuptools.setup` in :file:`setup.py`. For example:
 A complete working example of two pkg_resources-style namespace packages can be found
 in the `pkg_resources namespace example project`_.
 
-.. _setuptools: https://setuptools.readthedocs.io/en/latest/
 .. _pkg_resources.declare_namespace:
     https://setuptools.readthedocs.io/en/latest/pkg_resources.html#namespace-package-support
 .. _pkg_resources namespace example project:

source/guides/supporting-windows-using-appveyor.rst

@@ -241,4 +241,3 @@ For reference, the SDK setup support script is listed here:
 .. _Travis: https://travis-ci.org/
 .. _Github: https://github.com
 .. _Bitbucket: https://bitbucket.org/
-.. _Tox: https://tox.readthedocs.io/en/latest/