Skip to content

Commit 0671716

Browse files
committed
Clarify sentence about empty __init__.py
GitHub: fixes #1292
1 parent d3e161e commit 0671716

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

source/tutorials/packaging-projects.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -54,8 +54,8 @@ Create the following file structure locally:
5454
The directory containing the Python files should match the project name. This
5555
simplifies the configuration and is more obvious to users who install the package.
5656

57-
:file:`__init__.py` is required to import the directory as a package, and
58-
should be empty.
57+
:file:`__init__.py` is required to import the directory as a package,
58+
even if as is our case for this tutorial that file is empty.
5959

6060
:file:`example.py` is an example of a module within the package that could
6161
contain the logic (functions, classes, constants, etc.) of your package.
@@ -107,7 +107,7 @@ Choosing a build backend
107107
------------------------
108108

109109
Tools like :ref:`pip` and :ref:`build` do not actually convert your sources
110-
into a :term:`distribution package <Distribution Package>` (like a wheel);
110+
into a :term:`distribution package <Distribution Package>` (like a wheel);
111111
that job is performed by a *build backend*. The build backend determines how
112112
your project will specify its configuration, including metadata (information
113113
about the project, for example, the name and tags that are displayed on PyPI)

0 commit comments

Comments
 (0)