Development repo for evolution of PyPA interoperability standards (released versions are published as PEPs on python.org)
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
pep-0458-repository
schemas
unpublished
.gitignore
LICENSE
README.md
pep-0376-installation-db.rst
pep-0425-compatibility-tags.rst
pep-0426-core-metadata.rst
pep-0427-wheel-format.rst
pep-0440-versioning.rst
pep-0458-1.png
pep-0458-2.png
pep-0458-3.png
pep-0458-4.png
pep-0458-tuf-online-keys.rst
pep-0459-standard-metadata-extensions.rst
pep-0470-removal-of-external-hosting.rst
pep-0496-environment-markers.rst
pep-0503-simple-repository-protocol.rst
pep-0508-dependency-specifiers.rst
pep-0516-build-system-abstraction.rst
pep-0517-build-system-abstraction.rst

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.