summaryrefslogtreecommitdiff
path: root/docs/setuptools.txt
diff options
context:
space:
mode:
authorJason R. Coombs <jaraco@jaraco.com>2018-05-15 11:29:00 -0400
committerJason R. Coombs <jaraco@jaraco.com>2018-05-15 11:29:00 -0400
commit0088027f2798fe35d0101451ccbdcf62ccee282c (patch)
tree0832193411366cc71d851d8ff3e9af1e8de50f7c /docs/setuptools.txt
parent26b75f5151a761f3206b0dbf68f4e56363ca2ed4 (diff)
downloadpython-setuptools-git-0088027f2798fe35d0101451ccbdcf62ccee282c.tar.gz
Add the phrase declarative config for easier searching
Diffstat (limited to 'docs/setuptools.txt')
-rw-r--r--docs/setuptools.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/setuptools.txt b/docs/setuptools.txt
index 5ee967ab..5af76c3e 100644
--- a/docs/setuptools.txt
+++ b/docs/setuptools.txt
@@ -437,7 +437,7 @@ such projects also need something like ``package_dir={'':'src'}`` in their
Anyway, ``find_packages()`` walks the target directory, filtering by inclusion
patterns, and finds Python packages (any directory). Packages are only
-recognized if they include an ``__init__.py`` file. Finally, exclusion
+recognized if they include an ``__init__.py`` file. Finally, exclusion
patterns are applied to remove matching packages.
Inclusion and exclusion patterns are package names, optionally including
@@ -2305,7 +2305,7 @@ Configuring setup() using setup.cfg files
``Setuptools`` allows using configuration files (usually :file:`setup.cfg`)
to define a package’s metadata and other options that are normally supplied
-to the ``setup()`` function.
+to the ``setup()`` function (declarative config).
This approach not only allows automation scenarios but also reduces
boilerplate code in some cases.