@@ -7,7 +7,7 @@ Status: Draft
7
7
Type: Standards Track
8
8
Content-Type: text/x-rst
9
9
Created: 08-Mar-2022
10
- Post-History: 08-Mar-2022
10
+ Post-History: ` 08-Mar-2022 < https://discuss.python.org/t/14141 >`__
11
11
12
12
13
13
Abstract
@@ -64,10 +64,10 @@ Runs of ``.`` and ``-``, unlike PEP 503, do **not** get collapsed,
64
64
e.g. ``.. `` stays the same.
65
65
66
66
For pip 22, its
67
- "extra normalisation behaviour is quite convoluted and erratic" [ pip-erratic ]_ ,
67
+ ` "extra normalisation behaviour is quite convoluted and erratic" < pip-erratic _>`__ ,
68
68
and so its use is not considered.
69
69
70
- .. [ pip -erratic] https://discuss.python.org/t/what-extras-names-are-treated-as-equal-and-why/ 7614/10?
70
+ .. _ pip -erratic: https://discuss.python.org/t/7614/10
71
71
72
72
73
73
Specification
@@ -99,7 +99,7 @@ tools SHOULD warn the user.
99
99
Tools SHOULD warn users when an invalid extra name is read and not use
100
100
the name to avoid ambiguity.
101
101
Tools MAY raise an error instead of a warning when reading an
102
- invalid name if they so desire.
102
+ invalid name, if they so desire.
103
103
104
104
105
105
Backwards Compatibility
@@ -108,20 +108,20 @@ Backwards Compatibility
108
108
Moving to :pep: `503 ` normalization and :pep: `508 ` name acceptance, it
109
109
allows for all preexisting, valid names to continue to be valid.
110
110
111
- Based on research looking at a collection of wheels on PyPI [ pypi-results ]_ ,
111
+ Based on ` research looking at a collection of wheels on PyPI < pypi-results _>`__ ,
112
112
the risk of extra name clashes is limited to 73 clashes when considering
113
113
even invalid names,
114
114
while *only * looking at valid names leads to only 3 clashes:
115
115
116
- 1. dev-test: dev_test, dev-test, dev.test
117
- 2. dev-lint: dev-lint, dev.lint, dev_lint
118
- 3. apache-beam: apache-beam, apache.beam
116
+ * `` dev-test ``: `` dev_test ``, `` dev-test ``, `` dev.test ``
117
+ * `` dev-lint ``: `` dev-lint ``, `` dev.lint ``, `` dev_lint ``
118
+ * `` apache-beam ``: `` apache-beam ``, `` apache.beam ``
119
119
120
120
By requiring tools writing core metadata to only record the normalized name,
121
121
the issue of preexisting, invalid extra names should be diminished over
122
122
time.
123
123
124
- .. [ pypi -results] https://discuss.python.org/t/pep-685-comparison-of-extra-names-for-optional-distribution-dependencies/ 14141/17?u=brettcannon
124
+ .. _ pypi -results: https://discuss.python.org/t/14141/17
125
125
126
126
127
127
Security Implications
@@ -162,7 +162,7 @@ Rejected Ideas
162
162
Using setuptools 60's normalization
163
163
-----------------------------------
164
164
165
- Initially this PEP proposed following setuptools to try and minimize
165
+ Initially, this PEP proposed following setuptools to try to minimize
166
166
backwards-compatibility issues.
167
167
But after checking various wheels on PyPI,
168
168
it became clear that standardizing **all ** naming on :pep: `508 ` and
0 commit comments