Skip to content
This repository has been archived by the owner on Feb 27, 2024. It is now read-only.
/ interoperability-peps Public archive

Development repo for evolution of PyPA interoperability standards (released versions are published as PEPs on python.org)

License

Notifications You must be signed in to change notification settings

pypa/interoperability-peps

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

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 PSF Code of Conduct.

About

Development repo for evolution of PyPA interoperability standards (released versions are published as PEPs on python.org)

Resources

License

Code of conduct

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages