Explicitly call out limiting sdists to one per release (#75)
This commit is contained in:
parent
085703bc03
commit
20acfcb7a2
20
pep-0527.txt
20
pep-0527.txt
|
@ -26,6 +26,10 @@ In addition, this PEP proposes removing support for new uploads of sdists using
|
|||
the ``.tar``, ``.tar.bz2``, ``.tar.xz``, ``.tar.Z``, ``.tgz``, ``.tbz``, and
|
||||
any other extension besides ``.tar.gz`` and ``.zip``.
|
||||
|
||||
Finally, this PEP also proposes limiting the number of allowed sdist uploads
|
||||
for each individual release of a project on PyPI to one instead of one for each
|
||||
allowed extension.
|
||||
|
||||
|
||||
Rationale
|
||||
=========
|
||||
|
@ -193,6 +197,22 @@ format also uses zip.
|
|||
Instead of trying to standardize on either ``.tar.gz`` or ``.zip``, this PEP
|
||||
proposes that we allow *either* ``.tar.gz`` or ``.zip`` for sdists.
|
||||
|
||||
|
||||
Limiting number of sdists per release
|
||||
-------------------------------------
|
||||
|
||||
A sdist on PyPI should be a single source of truth for a particular release of
|
||||
software. However, currently PyPI allows you to upload one sdist for each of
|
||||
the sdist file extensions it allows. Currently this allows something like 10
|
||||
different sdists for a project, but even with this PEP it allows two different
|
||||
sources of truth for a single version. Having multiple sdists often times can
|
||||
account for strange bugs that only expose themselves based on which sdist that
|
||||
the person used.
|
||||
|
||||
To resolve this, this PEP proposes to allow one, and only one, sdist per
|
||||
release of a project.
|
||||
|
||||
|
||||
Removal Process
|
||||
===============
|
||||
|
||||
|
|
Loading…
Reference in New Issue