PEP 643: Add Discussions-To and clarify handling of Python-Requires (#1689)

This commit is contained in:
Paul Moore 2020-10-26 19:22:26 +00:00 committed by GitHub
parent 4f140e4fcd
commit e56630a365
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 1 deletions

View File

@ -2,7 +2,7 @@ PEP: 643
Title: Metadata for Package Source Distributions Title: Metadata for Package Source Distributions
Author: Paul Moore <p.f.moore@gmail.com> Author: Paul Moore <p.f.moore@gmail.com>
BDFL-Delegate: Paul Ganssle <paul@ganssle.io> BDFL-Delegate: Paul Ganssle <paul@ganssle.io>
Discussions-To: Discourse, thread to be created. Discussions-To: https://discuss.python.org/t/pep-643-metadata-for-package-source-distributions/5577
Status: Draft Status: Draft
Type: Standards Track Type: Standards Track
Content-Type: text/x-rst Content-Type: text/x-rst
@ -116,6 +116,15 @@ format to version 2.2.
Source distributions MUST use the latest version of the core metadata Source distributions MUST use the latest version of the core metadata
specification (which will be version 2.2 or later). specification (which will be version 2.2 or later).
The ``Requires-Python`` field for a project may vary by target platform,
but is not allowed to be declared as ``Dynamic`` in the sdist metadata.
To handle this situation, build backends MUST use environment markers on
the ``Requires-Python`` field to allow that metadata to remain common
across the sdist and all wheel archives, rather than generating platform
dependent ``Requires-Python`` metadata as part of the wheel build
process. Build backends SHOULD also use this approach for other
metadata fields that may vary by target platform (e.g. dependency
declarations).
Backwards Compatibility Backwards Compatibility
======================= =======================