[Python-checkins] peps: pep-0426: don't require Provides-Dist: our name

[daniel.holth]

http://hg.python.org/peps/rev/08105ae9d5af
changeset:   4734:08105ae9d5af
user:        Daniel Holth <dholth at fastmail.fm>
date:        Mon Feb 11 22:49:33 2013 -0500
summary:
  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.

files:
  pep-0426.txt |  17 ++++-------------
  1 files changed, 4 insertions(+), 13 deletions(-)


diff --git a/pep-0426.txt b/pep-0426.txt
--- a/pep-0426.txt
+++ b/pep-0426.txt
@@ -43,7 +43,7 @@
 distribution.
 
 This format is parseable by the ``email`` module with an appropriate
-``email.policy.Policy()``. When ``metadata`` is a Unicode string,
+``email.policy.Policy()``.  When ``metadata`` is a Unicode string,
 ```email.parser.Parser().parsestr(metadata)`` is a serviceable parser.
 
 There are two standard locations for these metadata files:
@@ -277,11 +277,6 @@
 ``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 @@
 ----------------------------------
 
 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 @@
     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 @@
     Description: Description
         ===========
 
-
         A description of the package.
 
     """

-- 
Repository URL: http://hg.python.org/peps