[Python-checkins] r77343 - peps/trunk/pep-0345.txt

tarek.ziade python-checkins at python.org
Thu Jan 7 13:13:35 CET 2010


Author: tarek.ziade
Date: Thu Jan  7 13:13:35 2010
New Revision: 77343

Log:
remove occurences of 'package' that means 'distribution' here

Modified:
   peps/trunk/pep-0345.txt

Modified: peps/trunk/pep-0345.txt
==============================================================================
--- peps/trunk/pep-0345.txt	(original)
+++ peps/trunk/pep-0345.txt	Thu Jan  7 13:13:35 2010
@@ -57,7 +57,7 @@
 Name
 ::::
 
-The name of the package.
+The name of the distributions.
 
 Example::
 
@@ -67,7 +67,7 @@
 Version
 :::::::
 
-A string containing the package's version number.  This
+A string containing the distribution's version number.  This
 field  must be in the format specified in PEP 386.
 
 Example::
@@ -79,7 +79,7 @@
 :::::::::::::::::::::::
 
 A Platform specification describing an operating system supported by
-the package which is not listed in the "Operating System" Trove classifiers.
+the distribution which is not listed in the "Operating System" Trove classifiers.
 See "Classifier" below.
 
 Examples::
@@ -93,7 +93,7 @@
 
 Binary distributions containing a PKG-INFO file will use the
 Supported-Platform field in their metadata to specify the OS and
-CPU for which the binary package was compiled.  The semantics of
+CPU for which the binary distribution was compiled.  The semantics of
 the Supported-Platform field are not specified in this PEP.
 
 Example::
@@ -105,7 +105,7 @@
 Summary
 :::::::
 
-A one-line summary of what the package does.
+A one-line summary of what the distribution does.
 
 Example::
 
@@ -115,7 +115,7 @@
 Description (optional)
 ::::::::::::::::::::::
 
-A longer description of the package that can run to several
+A longer description of the distribution that can run to several
 paragraphs.  Software that deals with metadata should not assume
 any maximum size for this field, though people shouldn't include
 their instruction manual as the description.
@@ -152,7 +152,7 @@
 :::::::::::::::::::
 
 A list of additional keywords to be used to assist searching
-for the package in a larger catalog.
+for the distribution in a larger catalog.
 
 Example::
 
@@ -162,7 +162,7 @@
 Home-page (optional)
 ::::::::::::::::::::
 
-A string containing the URL for the package's home page.
+A string containing the URL for the distribution's home page.
 
 Example::
 
@@ -172,9 +172,9 @@
 Download-URL
 ::::::::::::
 
-A string containing the URL from which this version of the package
+A string containing the URL from which this version of the distribution
 can be downloaded.  (This means that the URL can't be something like
-".../package-latest.tgz", but instead must be ".../package-0.45.tgz".)
+".../BeagleVote-latest.tgz", but instead must be ".../BeagleVote-0.45.tgz".)
 
 
 Author (optional)
@@ -214,7 +214,7 @@
 A string containing the maintainer's name at a minimum; additional
 contact information may be provided.
 
-Note that this field is intended for use when a package is being
+Note that this field is intended for use when a project is being
 maintained by someone other than the original author:  it should be
 omitted if it is identical to ``Author``.
 
@@ -231,7 +231,7 @@
 a name and e-mail address in the legal forms for a RFC-822
 ``From:`` header.
 
-Note that this field is intended for use when a package is being
+Note that this field is intended for use when a project is being
 maintained by someone other than the original author:  it should be
 omitted if it is identical to ``Author-email``.
 
@@ -243,7 +243,7 @@
 License (optional)
 ::::::::::::::::::
 
-Text indicating the license covering the package where the license
+Text indicating the license covering the distribution where the license
 is not a selection from the "License" Trove classifiers. See
 "Classifier" below.  This field may also be used to specify a
 particular version of a licencse which is named via the ``Classifier``
@@ -262,7 +262,7 @@
 :::::::::::::::::::::::::
 
 Each entry is a string giving a single classification value
-for the package.  Classifiers are described in PEP 301 [2].
+for the distribution.  Classifiers are described in PEP 301 [2].
 
 Examples::
 
@@ -274,7 +274,7 @@
 ::::::::::::::::::::::::::::
 
 Each entry contains a string naming some other distutils
-project required by this package.
+project required by this distribution.
 
 The format of a requirement string is identical to that of a
 distutils project name (e.g., as found in the ``Name:`` field.
@@ -321,16 +321,16 @@
 
 Examples::
 
-    Provides-Dist: OtherPackage
-    Provides-Dist: AnotherPackage (3.4)
+    Provides-Dist: OtherProject
+    Provides-Dist: AnotherProject (3.4)
     Provides-Dist: virtual_package
 
 
 Obsoletes-Dist (multiple use)
 :::::::::::::::::::::::::::::
 
-Each entry contains a string describing a distutils project which
-this package renders obsolete, meaning that the two packages
+Each entry contains a string describing a distutils project's distribution
+which this distribution renders obsolete, meaning that the two projects
 should not be installed at the same time.
 
 Version declarations can be supplied.  Version numbers must be in the
@@ -344,13 +344,13 @@
 Examples::
 
     Obsoletes-Dist: Gorgon
-    Obsoletes-Dist: OtherPackage (<3.0)
+    Obsoletes-Dist: OtherProject (<3.0)
 
 
 Requires-Python
 :::::::::::::::
 
-This field specifies the Python version(s) that the package is
+This field specifies the Python version(s) that the distribution is
 guaranteed to be compatible with.
 
 Version numbers must be in the format specified in `Version Specifiers`_.
@@ -367,9 +367,9 @@
 ::::::::::::::::::::::::::::::::
 
 Each entry contains a string describing some dependency in the
-system that the package is to be used.  This field is intended to
-serve as a hint to downstream package maintainers, and has no
-semantics which are meaningful to the ``distutils`` package.
+system that the distribution is to be used.  This field is intended to
+serve as a hint to downstream project maintainers, and has no
+semantics which are meaningful to the ``distutils`` distribution.
 
 The format of a requirement string is a name of an external
 dependency, optionally followed by a version declaration within


More information about the Python-checkins mailing list