[Python-checkins] peps: Officially defer PEP 426 (Metadata 2.0)
nick.coghlan
python-checkins at python.org
Thu Jun 2 15:11:37 EDT 2016
https://hg.python.org/peps/rev/94c1afae202e
changeset: 6346:94c1afae202e
user: Nick Coghlan <ncoghlan at gmail.com>
date: Thu Jun 02 12:11:25 2016 -0700
summary:
Officially defer PEP 426 (Metadata 2.0)
files:
pep-0426.txt | 49 +++++++++++++++++++++++----------------
1 files changed, 29 insertions(+), 20 deletions(-)
diff --git a/pep-0426.txt b/pep-0426.txt
--- a/pep-0426.txt
+++ b/pep-0426.txt
@@ -7,7 +7,7 @@
Donald Stufft <donald at stufft.io>
BDFL-Delegate: Nick Coghlan <ncoghlan at gmail.com>
Discussions-To: Distutils SIG <distutils-sig at python.org>
-Status: Draft
+Status: Deferred
Type: Standards Track
Content-Type: text/x-rst
Requires: 440
@@ -39,13 +39,37 @@
several issues with the previous iteration of the standard version
identification scheme.
+PEP Deferral
+============
+
+Migrating to a new metadata format is current deferred indefinitely, with
+distutils-sig instead focusing on a more incremental approach to allowing
+parts of the ecosystem to be independently upgraded without breaking the world.
+
+Some of those incremental improvements include:
+
+* PEP 425, defining a compatibility tagging mechanism for binary files
+* PEP 427, defining the pre-built "wheel" format
+* PEP 440, covering the versioning identification and selection scheme
+* PEP 503, ``/simple/`` package repository API
+* PEP 508, covering dependency declarations and environment markers
+* PEP 513, defining the "manylinux1" compatibility tag
+* PEP 518, defining a static config file for sdist build system dependencies
+
+Other planned improvements in various stages of development include:
+
+* Supporting build systems that don't provide the `setup.py` command
+* Supporting additional semantic categories for distribution contents (based on
+ GNU autotools)
+* Support for declaring dependencies on shared system libraries
+
.. note::
"I" in this doc refers to Nick Coghlan. Daniel and Donald either wrote or
- contributed to earlier versions, and have been providing feedback as this
- JSON-based rewrite has taken shape. Daniel and Donald have also been
- vetting the proposal as we go to ensure it is practical to implement for
- both clients and index servers.
+ contributed to earlier versions, and provided feedback as the JSON-based
+ rewrite took shape. Daniel and Donald were also vetting the proposal as we
+ went to ensure it remained practical to implement for both clients and
+ index servers.
Metadata 2.0 represents a major upgrade to the Python packaging ecosystem,
and attempts to incorporate experience gained over the 15 years(!) since
@@ -58,21 +82,6 @@
source packages for at least Debian and Fedora, and perhaps other
platform specific distribution systems).
- There will eventually be a suite of PEPs covering various aspects of
- the metadata 2.0 format and related systems:
-
- * this PEP, covering the core metadata format
- * PEP 440, covering the versioning identification and selection scheme
- * PEP 459, covering several standard extensions
- * PEP 496, covering environment markers
- * a yet-to-be-written PEP to define v2.0 of the sdist format
- * an updated wheel PEP (v1.1) to add pydist.json (and possibly convert
- the wheel metadata file from Key:Value to JSON)
- * an updated installation database PEP to add pydist.json
- * a PEP to standardise the expected command line interface for setup.py
- as an interface to an application's build system (rather than requiring
- that the build system support the distutils command system)
-
It's going to take a while to work through all of these and make them
a reality. The main change from our last attempt at this is that we're
trying to design the different pieces so we can implement them
--
Repository URL: https://hg.python.org/peps
More information about the Python-checkins
mailing list