peps: 74868fe8ba17 (original) (raw)

--- a/pep-0426.txt +++ b/pep-0426.txt @@ -26,16 +26,17 @@ Version 1.3 of the metadata format adds third-party packaging of Python Software easier and defines a formal extension mechanism. The fields are "Setup-Requires-Dist" "Provides-Extra", and "Extension". This version also adds the extra -variable to the environment markers specification. +variable to the environment markers specification and allows the +description to be placed into a payload section. Metadata Files ============== The syntax defined in this PEP is for use with Python distribution metadata files. The file format is a simple UTF-8 encoded Key: value -format with no maximum line length. It is parseable by the email -module with an appropriate email.policy.Policy(). The field names -listed in the Fields_ section are used as the header names. +format with no maximum line length, followed by a blank line and an +arbitrary payload. It is parseable by the email module with an +appropriate email.policy.Policy(). In Python 3.2, a serviceable read-only parser is:: @@ -46,12 +47,10 @@ There are two standard locations for the

- -This encoding implies that any occurences of a CRLF followed by 7 spaces -and a pipe char have to be replaced by a single CRLF when the field is unfolded -using a RFC822 reader. - +Since Metadata 1.3 the recommended place for the description is in the +payload section of the document, after the last header. The description +needs no special formatting when included in the payload. Keywords (optional) ::::::::::::::::::: @@ -278,6 +262,9 @@ Examples:: License: GPL version 3, excluding DRM provisions +The full text of the license would normally be included in a separate +file. + Classifier (multiple use) ::::::::::::::::::::::::: @@ -608,21 +595,24 @@ The fields that benefit from this marker Summary of Differences From PEP 345 =================================== -* Values are now expected to be UTF-8 +* Metadata-Version is now 1.3. -* Metadata-Version is now 1.3. +* Values are now expected to be UTF-8. + +* A payload (containing the description) may appear after the headers.

+Appendix +======== + +Parsing and generating the Metadata 1.3 serialization format using +Python 3.3:: +

+

+

+

+

+

+

+

+

Copyright =========