Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions source/tutorials/packaging-projects.rst
Original file line number Diff line number Diff line change
Expand Up @@ -54,8 +54,8 @@ Create the following file structure locally:
The directory containing the Python files should match the project name. This
simplifies the configuration and is more obvious to users who install the package.

:file:`__init__.py` is required to import the directory as a package, and
should be empty.
:file:`__init__.py` is required to import the directory as a package,
even if as is our case for this tutorial that file is empty.
Comment thread
sinoroc marked this conversation as resolved.

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

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