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

Specify where to send discussions for PEP 621 (#1447)

This commit is contained in:
Brett Cannon 2020-06-22 14:58:41 -07:00 committed by GitHub
parent 88a5ace0fb
commit 977f841a11
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
pep-0621.rst
View File

@ -8,6 +8,7 @@ Author: Brett Cannon <brett@python.org>,
Sébastien Eustace <sebastien@eustace.io>,
Thomas Kluyver <thomas@kluyver.me.uk>,
Tzu-Ping Chung <uranusjr@gmail.com>
Discussions-To: https://discuss.python.org/t/pep-621-storing-project-metadata-in-pyproject-toml/4513
Status: Draft
Type: Standards Track
Content-Type: text/x-rst
@ -646,7 +647,7 @@ waiting until the user has run a tool in the case of :pep:`508`'s DSL.
Supporters also believe it is easier to read and reason (both in
general and for first-time users). They also point out that other
programming languages have adopted a format more like an exploded
table thanks to their use standardized configuration formats (e.g.
table thanks to their use of standardized configuration formats (e.g.
`Rust <https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html>`__,
and `Dart <https://dart.dev/tools/pub/dependencies>`__). The thinking
is that an exploded table format would be more familiar to people