From 0342a80a0610d358984764eb527ed54d0fee3aed Mon Sep 17 00:00:00 2001 From: Steve Piercy Date: Wed, 24 Dec 2025 02:09:19 -0800 Subject: [PATCH 1/2] Clarify native and implicit namespace package terminology Explain that native and implicit namespace packages are the same PEP 420 mechanism, and describe both terms in the namespace packaging guide. Keep the detailed terminology on the guide page rather than adding separate glossary entries. --- source/guides/packaging-namespace-packages.rst | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/source/guides/packaging-namespace-packages.rst b/source/guides/packaging-namespace-packages.rst index 6ff93c4c9a..00320d5ed4 100644 --- a/source/guides/packaging-namespace-packages.rst +++ b/source/guides/packaging-namespace-packages.rst @@ -71,6 +71,21 @@ from which the latter is discouraged: #. Use `legacy namespace packages`_. This comprises `pkgutil-style namespace packages`_ and `pkg_resources-style namespace packages`_. +.. note:: + + "Native namespace packages" and "implicit namespace packages" are two names for + the same type of namespace package. It's defined in :pep:`420`, and is available + in Python 3.3 and later. + + The term "native" derives from the built-in feature of Python to create packages + without installing an extra package, such as setuptools, from outside the standard + library. The term "implicit" derives from the fact that you don't have to explicitly + declare the namespace package in a :file:`__init__.py` file. + + This guide uses these names interchangeably. + +.. _native-namespace-packages: + Native namespace packages ------------------------- From 6b3bd1dfe8f5d69522a555007e9ac4444a02b3e6 Mon Sep 17 00:00:00 2001 From: Ralf Gommers Date: Sat, 14 Nov 2026 10:43:32 +0000 Subject: [PATCH 2/2] Link namespace package glossary entry to the guide; remove duplicate sentence Point readers to the namespace packaging guide for the native and legacy approaches, keeping the glossary definition concise. The sentence on PEP 420 and Python 3.3 is already present in the numbered list right above, so remove it - this also makes the added .. note:: more concise. --- source/glossary.rst | 3 +++ source/guides/packaging-namespace-packages.rst | 13 +++++-------- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/source/glossary.rst b/source/glossary.rst index 4ac30f512c..31c8cb1153 100644 --- a/source/glossary.rst +++ b/source/glossary.rst @@ -192,6 +192,9 @@ Glossary A mechanism for splitting a single :term:`Import Package ` across one or more :term:`Distribution Packages `. + For guidance on creating namespace packages, see + :ref:`packaging-namespace-packages`. + Package Index diff --git a/source/guides/packaging-namespace-packages.rst b/source/guides/packaging-namespace-packages.rst index 00320d5ed4..2cb590d053 100644 --- a/source/guides/packaging-namespace-packages.rst +++ b/source/guides/packaging-namespace-packages.rst @@ -74,14 +74,11 @@ from which the latter is discouraged: .. note:: "Native namespace packages" and "implicit namespace packages" are two names for - the same type of namespace package. It's defined in :pep:`420`, and is available - in Python 3.3 and later. - - The term "native" derives from the built-in feature of Python to create packages - without installing an extra package, such as setuptools, from outside the standard - library. The term "implicit" derives from the fact that you don't have to explicitly - declare the namespace package in a :file:`__init__.py` file. - + the same type of namespace package. The term "native" derives from the built-in + feature of Python to create packages without installing an extra package, such as + setuptools, from outside the standard library. The term "implicit" derives from + the fact that you don't have to explicitly declare the namespace package in a + :file:`__init__.py` file. This guide uses these names interchangeably. .. _native-namespace-packages: