To learn more about the purpose of PEPs and how to go about writing a PEP, please start reading at PEP 1 (pep-0001.txt in this repo). Note that PEP 0, the index PEP, is now automatically generated, and not committed to the repo.
Has this idea been proposed on python-ideas and received general acceptance as being an idea worth pursuing? (if not then please start a discussion there before submitting a pull request).
More details about it in PEP 1.
Do you have an implementation of your idea? (this is important for when you propose this PEP to python-dev as code maintenance is a critical aspect of all PEP proposals prior to a final decision; in special circumstances an implementation can be deferred)
When committing to a PEP, please always include the PEP number in the subject title. For example, PEP NNN: <summary of changes>.
Before you hit "Create pull request", please take a moment to ensure that this project can legally accept your contribution by verifying you have signed the PSF Contributor Agreement:
If you haven't signed the CLA before, please follow the steps outlined in the CPython devguide to do so:
Thanks again to your contribution and we look forward to looking at it!
All interactions for this project are covered by the PSF Code of Conduct. Everyone is expected to be open, considerate, and respectful of others no matter their position within the project.