iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 518: Clarify any tool can use the tool table (#1054) 

Context: https://discuss.python.org/t/pep-518-clarify-scope-of-tool-section/1682
This commit is contained in:
Ethan Smith 2019-05-15 23:33:02 -07:00 committed by Nathaniel J. Smith
parent aceed0d7c0
commit b5a4f071d5
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
pep-0518.txt
View File

@ -193,10 +193,11 @@ second option to help people move over to ``pyproject.toml`` files.
tool table
----------
The ``[tool]`` table is where tools can have users specify
configuration data as long as they use a sub-table within ``[tool]``,
e.g. the `flit <https://pypi.python.org/pypi/flit>`_ tool would store
its configuration in ``[tool.flit]``.
The ``[tool]`` table is where any tool related to your Python
project, not just build tools, can have users specify configuration
data as long as they use a sub-table within ``[tool]``, e.g. the
`flit <https://pypi.python.org/pypi/flit>`_ tool would store its
configuration in ``[tool.flit]``.
We need some mechanism to allocate names within the ``tool.*``
namespace, to make sure that different projects don't attempt to use