summaryrefslogtreecommitdiff
path: root/docs/setuptools.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/setuptools.rst')
-rw-r--r--docs/setuptools.rst20
1 files changed, 17 insertions, 3 deletions
diff --git a/docs/setuptools.rst b/docs/setuptools.rst
index d0fb9a9c..53170589 100644
--- a/docs/setuptools.rst
+++ b/docs/setuptools.rst
@@ -21,8 +21,9 @@ Feature Highlights:
individually in setup.py
* Automatically include all relevant files in your source distributions,
- without needing to create a ``MANIFEST.in`` file, and without having to force
- regeneration of the ``MANIFEST`` file when your source tree changes.
+ without needing to create a |MANIFEST.in|_ file, and without having to force
+ regeneration of the ``MANIFEST`` file when your source tree changes
+ [#manifest]_.
* Automatically generate wrapper scripts or Windows (console and GUI) .exe
files for any number of "main" functions in your project. (Note: this is not
@@ -150,7 +151,6 @@ To use this feature:
[build-system]
requires = [
"setuptools >= 40.9.0",
- "wheel",
]
build-backend = "setuptools.build_meta"
@@ -211,3 +211,17 @@ set of steps to reproduce.
.. _GitHub Discussions: https://github.com/pypa/setuptools/discussions
.. _setuptools bug tracker: https://github.com/pypa/setuptools/
+
+
+----
+
+
+.. [#manifest] The default behaviour for ``setuptools`` will work well for pure
+ Python packages, or packages with simple C extensions (that don't require
+ any special C header). See :ref:`Controlling files in the distribution` and
+ :doc:`userguide/datafiles` for more information about complex scenarios, if
+ you want to include other types of files.
+
+
+.. |MANIFEST.in| replace:: ``MANIFEST.in``
+.. _MANIFEST.in: https://packaging.python.org/en/latest/guides/using-manifest-in/