Skip to content

Commit 766b8b9

Browse files
chryslesinoroc
andauthored
Highlight regular package as opposite to namespace package
And shorten `[build-system]` table. Co-authored-by: sinoroc <[email protected]>
1 parent f78f75f commit 766b8b9

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

source/guides/packaging-namespace-packages.rst

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ structure (following :ref:`src-layout <setuptools:src-layout>`):
8585
mynamespace/ # namespace package
8686
# No __init__.py here.
8787
subpackage_a/
88-
# Sub-packages have an __init__.py.
88+
# Regular import packages have an __init__.py.
8989
__init__.py
9090
module.py
9191
@@ -102,8 +102,7 @@ yourself, this is possible to be configured in the top-level :file:`pyproject.to
102102
.. code-block:: toml
103103
104104
[build-system]
105-
requires = ["setuptools", "setuptools-scm"]
106-
build-backend = "setuptools.build_meta"
105+
...
107106
108107
[tool.setuptools.packages.find]
109108
where = ["src/"]
@@ -188,7 +187,7 @@ To create a pkgutil-style namespace package, you need to provide an
188187
mynamespace/
189188
__init__.py # Namespace package __init__.py
190189
subpackage_a/
191-
__init__.py # Sub-package __init__.py
190+
__init__.py # Regular package __init__.py
192191
module.py
193192
194193
The :file:`__init__.py` file for the namespace package needs to contain
@@ -235,7 +234,7 @@ To create a pkg_resources-style namespace package, you need to provide an
235234
mynamespace/
236235
__init__.py # Namespace package __init__.py
237236
subpackage_a/
238-
__init__.py # Sub-package __init__.py
237+
__init__.py # Regular package __init__.py
239238
module.py
240239
241240
The :file:`__init__.py` file for the namespace package needs to contain

0 commit comments

Comments
 (0)