iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

pep-0426: don't require Provides-Dist: our name 

DRY rule for Provides-Dist: distributions always provide their own name.

No point asking projects to choose their metadata version; wacky version
numbers will not work correctly with tools regardless of the metadata
version.
This commit is contained in:
Daniel Holth 2013-02-11 22:49:33 -05:00
parent 2cda64a532
commit 1a1244b3ff
1 changed files with 4 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
pep-0426.txt
View File

@ -277,11 +277,6 @@ installing this distribution. These strings must be of the form
``Name`` or ``Name (Version)``, following the formats of the corresponding
field definitions.
For ease of metadata consumption, distributions are required to explicitly
include a ``Provides-Dist`` entry for their own name and version. This also
allows developers of a project to discourage users explicitly depending on
the project (by deliberately omitting this entry).
A distribution may provide additional names, e.g. to indicate that
multiple projects have been merged into and replaced by a single
distribution or to indicate that this project is a substitute for another.
@ -388,9 +383,9 @@ Setup-Requires-Dist (multiple use)
----------------------------------
Like ``Requires-Dist``, but names dependencies needed in order to build,
package or install the distribution. Commonly used to bring in extra
compiler support or a package needed to generate a manifest from
version control.
package or install the distribution -- in distutils, a dependency imported
by ``setup.py`` itself. Commonly used to bring in extra compiler support
or a package needed to generate a manifest from version control.
Examples::
@ -552,9 +547,6 @@ Version identifiers must comply with the following scheme::
N[.N]+[{a|b|c|rc}N][.postN][.devN]
Version identifiers which do not comply with this scheme are an error.
Projects which wish to use non-compliant version identifiers must restrict
themselves to metadata v1.1 (PEP 314) or earlier, as those specifications
do not constrain the versioning scheme.
Any given version will be a "release", "pre-release", "post-release" or
"developmental release" as defined in the following sections.
@ -1408,7 +1400,6 @@ Python 3.3::
Description: Description
===========
A description of the package.
"""