Fist a reminder of what a PEP is and how PEPs are organised
PEP stands for Python Enhancement Proposal. A PEP is a design document providing information to the Python community, or describing a new feature for Python or its processes or environment. The PEP should provide a concise technical specification of the feature and a rationale for the feature.
There are three main types of PEP:
There is also meta-PEPs, which are Process PEPs mostly about PEPs. i.e PEP 0 and PEP 1.
For Python 3, numbers in the 3000s were used for Py3k-specific proposals. But now that all new features go into Python 3 only, the process is back to using numbers in the 100s again. Remember that numbers below 100 are meta-PEPs.
So now what PEPs should a Python dev know or at least read?