Repository navigation
Set a limit on version identifiters for new releases - #2163
JacobCoffee wants to merge 1 commit into
Conversation
|
Changes and clarifications to the spec are discussed first at https://discuss.python.org/c/packaging/14 After agreement, either clarifications are opened here or a PEP process is followed. |
|
@notatallshaw Sure, i'll do that. i was directed here when asking how a change like this should be brought up |
|
closing per DPO discussion - indexes can enact this via policy so I think its okay to no set a restriction for tools. if we want this in the future, maybe we re-open but soften the language from |
|
Per the discussion thread, I think a The "ensure numeric segments fit within 64 bits" guidance would also be good to include. |
PEP440 does not contain a limit. Can we please add one?
things like https://pypi.org/project/uselesscapitalquiz/ happen without it, and other issues arise not least of which is user a11y related to trying to fit/show all of the wild versioning
stats from pypi:
we have 9.9mm releases, median version is 5 characters, 99th percentil is 20, and maximal is 217(!!)
I propose a 128 char cap, 100 would affect ~9 current releases some releases in the last months with ~110-115 char versioning which I honestly don't understand but... whatever! 128 is fine.
If you'd like to be restrictive, 32 or 64 would be nicer to handle from a designer/UI perspective.
I am not certain on an edit being required to the PEP itself, I think adding a practical limit on PyPI regardless is possible but I would prefer to have it codified.
refs:
📚 Documentation preview 📚: https://python-packaging-user-guide--2163.org.readthedocs.build/en/2163/