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

Add 'Classifiers' field 

Add 'Open Issues' and 'References' section
This commit is contained in:
Andrew M. Kuchling 2003-04-29 17:31:16 +00:00
parent d54646a718
commit f753309a41
1 changed files with 38 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

44
pep-0314.txt
View File

@ -20,14 +20,14 @@ Introduction
This document specifies version 1.1 of the metadata format.
Version 1.0 is specified in PEP 241.
Including Metadata in Packages
The Distutils 'sdist' command will be modified to extract the
metadata fields from the arguments and write them to a file in the
generated zipfile or tarball. This file will be named PKG-INFO
and will be placed in the top directory of the source
distribution (where the README, INSTALL, and other files usually
go).
The Distutils 'sdist' command will extract the metadata fields
from the arguments and write them to a file in the generated
zipfile or tarball. This file will be named PKG-INFO and will be
placed in the top directory of the source distribution (where the
README, INSTALL, and other files usually go).
Developers may not provide their own PKG-INFO file. The "sdist"
command will, if it detects an existing PKG-INFO file, terminate
@ -216,6 +216,17 @@ Fields
Example:
License: MIT
Classifier (multiple use)
Each entry is a string giving a single classification value
for the package. Classifiers are described in PEP 301 [1].
Examples:
Classifier: Development Status :: 4 - Beta
Classifier: Environment :: Console (Text Based)
Requires (multiple use)
@ -300,11 +311,32 @@ Fields
Conflicts: Gorgon
Summary of Differences From PEP 241
* Metadata-Version is now 1.1.
* Added the Classifiers field from PEP 301.
* Added fields: Requires, Provides, Obsoletes, Conflicts.
Open issues
With the addition of the 'Classifiers' field, should the Platform
and License fields be removed?
Acknowledgements
None yet.
References
[1] PEP 301
http://www.python.org/peps/pep-0301.html
Copyright
This document has been placed in the public domain.