This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients docs@python, msmhrt, ncoghlan, r.david.murray
Date 2014-01-25.08:03:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390637020.22.0.200302460896.issue20330@psf.upfronthosting.co.za>
In-reply-to
Content
David is correct, most PEPs are historical records of design decisions that cease to be updated once completed. The language reference is the normative guide for current behaviour.

The exception is "informational" and "process" PEPs, which cover things that are not covered in the language reference, as well the occasional Standards Track PEP which ends up not being incorporated into the language reference properly (for example, until the import section was added to the language reference in Python 3.3, PEP 302 was the best available reference documentation).
History
Date User Action Args
2014-01-25 08:03:40ncoghlansetrecipients: + ncoghlan, r.david.murray, docs@python, msmhrt
2014-01-25 08:03:40ncoghlansetmessageid: <1390637020.22.0.200302460896.issue20330@psf.upfronthosting.co.za>
2014-01-25 08:03:40ncoghlanlinkissue20330 messages
2014-01-25 08:03:39ncoghlancreate