From e56630a3658389e075aa87c075cf88d636fcc7bf Mon Sep 17 00:00:00 2001 From: Paul Moore Date: Mon, 26 Oct 2020 19:22:26 +0000 Subject: [PATCH] PEP 643: Add Discussions-To and clarify handling of Python-Requires (#1689) --- pep-0643.rst | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/pep-0643.rst b/pep-0643.rst index 1f523f859..eab126631 100644 --- a/pep-0643.rst +++ b/pep-0643.rst @@ -2,7 +2,7 @@ PEP: 643 Title: Metadata for Package Source Distributions Author: Paul Moore BDFL-Delegate: Paul Ganssle -Discussions-To: Discourse, thread to be created. +Discussions-To: https://discuss.python.org/t/pep-643-metadata-for-package-source-distributions/5577 Status: Draft Type: Standards Track 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 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 =======================