From 0671716efede7103c3f80e10b642dc4fe036dd40 Mon Sep 17 00:00:00 2001 From: sinoroc Date: Sat, 4 Nov 2023 20:28:31 +0100 Subject: [PATCH] Clarify sentence about empty __init__.py GitHub: fixes https://github.com/pypa/packaging.python.org/issues/1292 --- source/tutorials/packaging-projects.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/tutorials/packaging-projects.rst b/source/tutorials/packaging-projects.rst index 0b6b60d81..5da846c9c 100644 --- a/source/tutorials/packaging-projects.rst +++ b/source/tutorials/packaging-projects.rst @@ -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. :file:`example.py` is an example of a module within the package that could contain the logic (functions, classes, constants, etc.) of your package. @@ -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 ` (like a wheel); +into a :term:`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)