diff options
| author | Hugo van Kemenade <hugovk@users.noreply.github.com> | 2023-01-14 17:05:03 +0200 |
|---|---|---|
| committer | Hugo van Kemenade <hugovk@users.noreply.github.com> | 2023-01-14 17:05:03 +0200 |
| commit | 20efb6fad4edf47fc56a1bcf44a7d1e5d646d02f (patch) | |
| tree | d7dfcacb7440b0d2dea394ba368c9c570a01835d /docs/userguide | |
| parent | 583836fd4110a03ac45a0e26ae58f54046de124b (diff) | |
| download | python-setuptools-git-20efb6fad4edf47fc56a1bcf44a7d1e5d646d02f.tar.gz | |
Use Sphinx :pep: role to link directly to PEPs
Diffstat (limited to 'docs/userguide')
| -rw-r--r-- | docs/userguide/package_discovery.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/userguide/package_discovery.rst b/docs/userguide/package_discovery.rst index 7dda84a8..9577a534 100644 --- a/docs/userguide/package_discovery.rst +++ b/docs/userguide/package_discovery.rst @@ -508,7 +508,7 @@ available to your interpreter. Legacy Namespace Packages ========================= The fact you can create namespace packages so effortlessly above is credited -to `PEP 420 <https://www.python.org/dev/peps/pep-0420/>`_. It used to be more +to :pep:`420`. It used to be more cumbersome to accomplish the same result. Historically, there were two methods to create namespace packages. One is the ``pkg_resources`` style supported by ``setuptools`` and the other one being ``pkgutils`` style offered by |