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

PEP 621: Cosmetic updates (#1459) 

A typo fix, and change email in example to a functional one.
This commit is contained in:
Pradyun Gedam 2020-06-24 10:55:03 +05:30 committed by GitHub
parent 5d2dc3fb23
commit 30592da944
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
pep-0621.rst
View File

@ -348,7 +348,7 @@ group. Its format is the same as ``[project.scripts]``.
The ``[project.entry-points]`` table is a collection of tables. Each
sub-table's name is an entry point group. The key and value semantics
are the same as ``[project.scripts]``. Users MUST not create
are the same as ``[project.scripts]``. Users MUST NOT create
nested sub-tables but instead keep the entry point groups to only one
level deep.
@ -427,7 +427,7 @@ Example
keywords = ["egg", "bacon", "sausage", "tomatoes", "Lobster Thermidor"]
authors = [
{name = "Brett Cannon", email = "brett@python.org"},
{email = "oss@pradyunsg.me"},
{email = "hi@pradyunsg.me"},
{name = "Tzu-Ping Chung"}
]
classifiers = [
@ -615,7 +615,7 @@ value types.
Backfilling trove classifiers SHOULD occur instead of MAY happen
----------------------------------------------------------------
Originally this PEP said that toosl SHOULD backfill appropriate trove classifiers.
Originally this PEP said that tools SHOULD backfill appropriate trove classifiers.
This was changed to say it MAY occur to emphasize it was entirely optional for
build back-ends to implement.