summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorJason R. Coombs <jaraco@jaraco.com>2020-05-03 05:59:41 -0400
committerGitHub <noreply@github.com>2020-05-03 05:59:41 -0400
commitcc5b5ec305100ecd897edfc7918f184ffc93c197 (patch)
treeb2004492da7532bfda879cb56450236bb37be282 /docs
parentd2a64aebe4fd7b02c9d05a0cac30faac38f18977 (diff)
downloadpython-setuptools-git-cc5b5ec305100ecd897edfc7918f184ffc93c197.tar.gz
Apply suggestions from code review
Diffstat (limited to 'docs')
-rw-r--r--docs/build_meta.txt12
1 files changed, 3 insertions, 9 deletions
diff --git a/docs/build_meta.txt b/docs/build_meta.txt
index 67497891..ef9fb2ac 100644
--- a/docs/build_meta.txt
+++ b/docs/build_meta.txt
@@ -34,12 +34,8 @@ package and distribute Python modules. Under PEP 517:
``pyproject.toml`` and decide what program to use to 'build from source'
(the default is ``setuptools``)
-With this standard, switching between packaging tools becomes a lot easier and
-in the case of ``setuptools``, ``setup.py`` becomes optional.
-
-``build_meta`` is ``setuptools``'s implementation of PEP 517. It provides the
-two functions, ``build_wheel`` and ``build_sdist`` amongst others, and uses
-a ``setup.cfg`` to specify the information about the package.
+With this standard, switching between packaging tools becomes a lot easier. ``build_meta``
+implements ``setuptools``' build system support.
How to use it?
--------------
@@ -60,9 +56,7 @@ setuptools, the content would be::
requires = ["setuptools", "wheel"]
build-backend = "setuptools.build_meta"
-Use ``setup.cfg`` to specify your package information, specified
-`here <https://setuptools.readthedocs.io/en/latest/setuptools.html#configuring
--setup-using-setup-cfg-files>`_ ::
+Use ``setuptools``' `declarative config`_ to specify the package information::
[metadata]
name = meowpkg