PEP 643: Clarify wording of rejected item about Requires-Python (GH-1719)

pep-0643.rst

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