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

PEP 566: More updates (#547) 

* PEP 566: Convert hyphens to underscores

* PEP 566: Update metadata version number

* PEP 566: Update acknowledgements
This commit is contained in:
Dustin Ingram 2018-01-22 18:14:49 -06:00 committed by Nick Coghlan
parent a459539920
commit e7cfcd5f01
1 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
pep-0566.txt
View File

@ -1,5 +1,5 @@
PEP: 566 PEP: 566
Title: Metadata for Python Software Packages 1.3 Title: Metadata for Python Software Packages 2.1
Version: $Revision$ Version: $Revision$
Last-Modified: $Date$ Last-Modified: $Date$
Author: Dustin Ingram <di@di.codes> Author: Dustin Ingram <di@di.codes>
@ -17,7 +17,7 @@ Replaces: 345
Abstract Abstract
======== ========
This PEP describes the changes between versions 1.2 and 1.3 of the core This PEP describes the changes between versions 1.2 and 2.1 of the core
metadata specification for Python packages. Version 1.2 is specified in PEP metadata specification for Python packages. Version 1.2 is specified in PEP
345. 345.
@ -36,7 +36,7 @@ PKG-INFO file. Other fields may only occur once in a PKG-INFO file. Fields
marked with "(optional)" are not required to appear in a valid PKG-INFO file; marked with "(optional)" are not required to appear in a valid PKG-INFO file;
all other fields must be present. all other fields must be present.
New in Version 1.3 New in Version 2.1
------------------ ------------------
Description-Content-Type (optional) Description-Content-Type (optional)
@ -72,7 +72,7 @@ environment markers which use extras.
The full specification for this field is defined in the `Core Metadata The full specification for this field is defined in the `Core Metadata
Specification`_. Specification`_.
Changed in Version 1.3 Changed in Version 2.1
---------------------- ----------------------
Name Name
@ -118,8 +118,8 @@ as follows:
#. The original key-value format should be read with #. The original key-value format should be read with
``email.parser.HeaderParser``; ``email.parser.HeaderParser``;
#. All transformed keys should be reduced to lower case, but otherwise should #. All transformed keys should be reduced to lower case. Hyphens should be
retain all other characters; replaced with underscores, but otherwise should retain all other characters;
#. The transformed value for any field marked with "(Multiple-use") should be a #. The transformed value for any field marked with "(Multiple-use") should be a
single list containing all the original values for the given key; single list containing all the original values for the given key;
#. The ``Keywords`` field should be converted to a list by splitting the #. The ``Keywords`` field should be converted to a list by splitting the
@ -129,7 +129,7 @@ as follows:
Summary of Differences From PEP 345 Summary of Differences From PEP 345
=================================== ===================================
* Metadata-Version is now 1.3. * Metadata-Version is now 2.1.
* Fields are now specified via the `Core Metadata Specification`_. * Fields are now specified via the `Core Metadata Specification`_.
@ -142,10 +142,11 @@ Summary of Differences From PEP 345
References References
========== ==========
This document specifies version 1.3 of the metadata format. This document specifies version 2.1 of the metadata format.
Version 1.0 is specified in PEP 241. Version 1.0 is specified in PEP 241.
Version 1.1 is specified in PEP 314. Version 1.1 is specified in PEP 314.
Version 1.2 is specified in PEP 345. Version 1.2 is specified in PEP 345.
Version 2.0, while not formally accepted, was specified in PEP 426.
.. _`Core Metadata Specification`: .. _`Core Metadata Specification`:
https://packaging.python.org/specifications/core-metadata/ https://packaging.python.org/specifications/core-metadata/
@ -158,7 +159,7 @@ This document has been placed in the public domain.
Acknowledgements Acknowledgements
================ ================
Thanks to Nick Coghlan for contributing to this PEP. Thanks to Nick Coghlan and Thomas Kluyver for contributing to this PEP.
.. ..