From d3a0a268fac9f257d254d9d8e6579fbe072315b1 Mon Sep 17 00:00:00 2001 From: "C.A.M. Gerlach" Date: Mon, 14 Mar 2022 13:21:26 -0500 Subject: [PATCH] PEP 685: Restore citations as originally intended --- pep-0685.rst | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/pep-0685.rst b/pep-0685.rst index c610b05539c..020aa33a825 100644 --- a/pep-0685.rst +++ b/pep-0685.rst @@ -66,10 +66,10 @@ docstring, which *does* specify that all non-alphanumeric characters (which would include ``-`` and ``.``) are normalized and collapsed. For pip 22, its -`"extra normalisation behaviour is quite convoluted and erratic" `__, +"extra normalisation behaviour is quite convoluted and erratic" [pip-erratic]_ and so its use is not considered. -.. _pip-erratic: https://discuss.python.org/t/7614/10 +.. [pip-erratic] Tzu-ping Chung on Python Discourse `__, +Based on research looking at a collection of wheels on PyPI [pypi-results]_, the risk of extra name clashes is limited to 73 instances when considering all extras names on PyPI, valid or not (not just those within a single package) while *only* looking at valid names leads to only 3 clashes: @@ -122,7 +122,7 @@ while *only* looking at valid names leads to only 3 clashes: By requiring tools writing core metadata to only record the normalized name, the issue of preexisting, invalid extra names should diminish over time. -.. _pypi-results: https://discuss.python.org/t/14141/17 +.. [pypi-results] Paul Moore on Python Discourse https://discuss.python.org/t/14141/17 Security Implications @@ -171,6 +171,12 @@ it became clear that standardizing **all** naming on :pep:`508` and while causing minimal backwards compatibility issues. +Open Issues +=========== + +N/A + + Copyright =========