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 lemburg
Recipients barry, gvanrossum, lemburg, michael.foord, ncoghlan, terry.reedy
Date 2013-07-27.10:00:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <51F39A33.6030206@egenix.com>
In-reply-to <1374907127.49.0.519033043684.issue18472@psf.upfronthosting.co.za>
Content
> 1. Added an intro paragraph that makes it clear this is a living document, not "set and forget".

If we want to make this a living document, I think the PEP will
have to receive its own internal version number and a history
section at the end explaining the changes (basically what you
just summarized for the patch).

Doing so is important, since companies and tools often reference
PEP 8 in internal coding guidelines and any changes need to
be easily identifiable for readers of those guidelines.
History
Date User Action Args
2013-07-27 10:00:22lemburgsetrecipients: + lemburg, gvanrossum, barry, terry.reedy, ncoghlan, michael.foord
2013-07-27 10:00:22lemburglinkissue18472 messages
2013-07-27 10:00:22lemburgcreate