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: Clarify wording of rejected item about Requires-Python (GH-1719)

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

18
pep-0643.rst
View File

@ -174,19 +174,13 @@ Rejected Ideas
does not seem to be enough benefit to this approach to make it worth does not seem to be enough benefit to this approach to make it worth
using instead of the proposed mechanism. using instead of the proposed mechanism.
3. Allow ``Requires-Python`` to be ``Dynamic``, as it cannot include 3. Special handling of ``Requires-Python``.
environment markers to tailor the requirement to the target
environment.
Currently, no projects on PyPI have a ``Requires-Python`` value that Early drafts of the PEP needed special discussion of ``Requires-Python``,
varies between different wheels for the same version, so there is no because the lack of environment markers for this field meant that it might
practical need for this flexibility at present. If a genuine use case be difficult to require it to be static. The final form of the PEP no longer
is identified later, the specification can be changed to allow needs this, as the idea of a whitelist of fields allowed to be dynamic was
``Requires-Python`` to be dynamic at that time. dropped.
In fact, this became irrelevant during subsequent discussions, when
the explicit whitelist of fields allowed to be ``Dynamic`` was
removed.
4. Restrict the use of ``Dynamic`` to a minimal "white list" of 4. Restrict the use of ``Dynamic`` to a minimal "white list" of
permitted fields. permitted fields.