summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJason R. Coombs <jaraco@jaraco.com>2020-05-10 15:11:22 -0400
committerGitHub <noreply@github.com>2020-05-10 15:11:22 -0400
commitb185376cb0d7d4ea01a5d69e4d4816548b2fe48a (patch)
tree4b57f901b4bdcd149c89f7a892be1b6a74041baa
parentd4fb0058d56bb03c97374665b62b6f0a1e586d49 (diff)
parent61ca49c08e71fee962b760fb90f8f89bb158738b (diff)
downloadpython-setuptools-git-b185376cb0d7d4ea01a5d69e4d4816548b2fe48a.tar.gz
Merge pull request #2091 from pganssle/setup_cfg_note
Tweak note about setup.cfg
-rw-r--r--docs/setuptools.txt5
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/setuptools.txt b/docs/setuptools.txt
index 22e3c872..30a30c26 100644
--- a/docs/setuptools.txt
+++ b/docs/setuptools.txt
@@ -2106,8 +2106,9 @@ Configuring setup() using setup.cfg files
.. note:: New in 30.3.0 (8 Dec 2016).
.. important::
- A ``setup.py`` file containing a ``setup()`` function call is still
- required even if your configuration resides in ``setup.cfg``.
+ If compatibility with legacy builds (i.e. those not using the :pep:`517`
+ build API) is desired, a ``setup.py`` file containing a ``setup()`` function
+ call is still required even if your configuration resides in ``setup.cfg``.
``Setuptools`` allows using configuration files (usually :file:`setup.cfg`)
to define a package’s metadata and other options that are normally supplied