The PEP process begins with a new idea for Python. This draft must be written in PEP style as described below. Reasons for denying PEP status include duplication of effort, being technically unsound, or not in keeping with the Python philosophy. The author of the PEP is then responsible for posting the PEP to the community forums, and marshaling community support for it. As updates are necessary, the PEP author can check in new versions if they have CVS commit permissions, or can email new PEP versions to the PEP editor for committing.
Standards track PEPs consists of two parts, a design document and a reference implementation.
PEP authors are responsible for collecting community feedback on a PEP before submitting it for review. However, wherever possible, long open-ended discussions on public mailing lists should be avoided. Once the authors have completed a PEP, they must inform the PEP editor that it is ready for review. Once a PEP has been accepted, the reference implementation must be completed. Once a PEP is deferred, the PEP editor can re-assign it to draft status.