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

PEP 643: Update Post-History and clarify permitted tool behaviour (GH-1704)

This commit is contained in:
Paul Moore 2020-11-02 19:06:09 +00:00 committed by GitHub
parent 954e0dc7b2
commit 3fb3e01471
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
pep-0643.rst
View File

@ -7,7 +7,7 @@ Status: Draft
Type: Standards Track Type: Standards Track
Content-Type: text/x-rst Content-Type: text/x-rst
Created: 24-Oct-2020 Created: 24-Oct-2020
Post-History: 24-Oct-2020 Post-History: 24-Oct-2020, 01-Nov-2020, 02-Nov-2020
Abstract Abstract
@ -86,6 +86,10 @@ This field will be multiple use, and will be allowed to contain the name
of another core metadata field. The ``Dynamic`` metadata item is only of another core metadata field. The ``Dynamic`` metadata item is only
allowed in source distribution metadata. allowed in source distribution metadata.
If tools that read metadata encounter the ``Dynamic`` field anywhere except
in a sdist, they MAY fail with an error. If they do not fail, they MUST
ignore the field, and may report a warning.
If a field is marked as ``Dynamic``, there is no restriction placed on If a field is marked as ``Dynamic``, there is no restriction placed on
its value in a wheel built from the sdist. A field which is marked as its value in a wheel built from the sdist. A field which is marked as
``Dynamic``, MUST NOT have an explicit value in the sdist. ``Dynamic``, MUST NOT have an explicit value in the sdist.