Development repo for evolution of PyPA interoperability standards (released versions are published as PEPs on python.org)
Python
Permalink
Failed to load latest commit information.
pep-0458-repository Add an example repository Jan 9, 2015
schemas Migrate content (no history) from BitBucket Dec 29, 2014
unpublished Assign PEP 517 Feb 18, 2016
.gitignore Initial commit Dec 29, 2014
LICENSE Initial commit Dec 29, 2014
README.md List the directories for the rendered copy Oct 28, 2015
pep-0376-installation-db.rst Migrate content (no history) from BitBucket Dec 29, 2014
pep-0425-compatibility-tags.rst Migrate content (no history) from BitBucket Dec 29, 2014
pep-0426-core-metadata.rst Migrate content (no history) from BitBucket Dec 29, 2014
pep-0427-wheel-format.rst Migrate content (no history) from BitBucket Dec 29, 2014
pep-0440-versioning.rst Delete references to PEP 426 in PEP 440 Dec 8, 2015
pep-0458-1.png Import the current state of PEP 458 Jan 2, 2015
pep-0458-2.png Update figures 2, 3, and 4 Jan 7, 2015
pep-0458-3.png Rename the online/offline and claimed/unclaimed terms in the figures Jan 14, 2015
pep-0458-4.png Rename the online/offline and claimed/unclaimed terms in the figures Jan 14, 2015
pep-0458-tuf-online-keys.rst Update pep-0458-tuf-online-keys.rst Nov 17, 2015
pep-0459-standard-metadata-extensions.rst Migrate content (no history) from BitBucket Dec 29, 2014
pep-0470-removal-of-external-hosting.rst PEP 470 is accepted Sep 2, 2015
pep-0496-environment-markers.rst Assign anvironment markers PEP as PEP 496 Aug 3, 2015
pep-0503-simple-repository-protocol.rst Accept the PEP Sep 24, 2015
pep-0508-dependency-specifiers.rst Merge pull request #61 from rbtcollins/dependency Feb 17, 2016
pep-0516-build-system-abstraction.rst Switch the BDFL-Delegate to Nick Feb 18, 2016
pep-0517-build-system-abstraction.rst Fix errors/warnings on PEP 517 Feb 18, 2016

README.md

PyPA Interoperability PEPs

This is the development repo for the definition and evolution of PyPA interoperability standards. Released versions of these standards are published as PEPs on python.org.

PEPs in this repo are always considered working drafts, regardless of their PEP metadata headers - the official versions are the ones published on python.org by the respective PEP authors and accepted by the assigned BDFL-Delegates.

Naming guidelines

To avoid folks needing to mentally map between the interoperability PEP numbers and their topics, the naming convention for PEPs in this repo is:

pep-<4 digit PEP number>-<topic>.rst

So, for example, the PEP 440 versioning specification is:

pep-0440-versioning.rst

Other directories

  • unpublished: draft documents that have yet to receive a PEP number
  • schemas: jsonschema files

Code of Conduct

Everyone interacting in the interoperability PEPs project's codebases, issue trackers, chat rooms, and mailing lists is expected to follow the PyPA Code of Conduct.