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 rhettinger
Recipients IanLee1521, docs@python, ezio.melotti, ncoghlan, rhettinger, terry.reedy
Date 2014-12-23.23:16:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1419376613.71.0.869174523479.issue23061@psf.upfronthosting.co.za>
In-reply-to
Content
> I would argue this is a good time to clean up that code in the standard library.

Please leave any clean-ups to the module maintainers.  PEP 8 is something you should do to your own code, rather than something you inflict on other people's code.

We generally leave "clean-ups" to the module maintainers rather than creating code churn which can make it more difficult to apply actual bug fixes across versions.

Also, GvR has long expressed a preference for "holistic refactoring" where we avoid making superficial changes across the library and reserve those changes for occasions where we're thinking more deeply about a specific piece of code.  The basis for this viewpoint has been confirmed a number of times when we've received Pep 8 patches that introduced bugs into code that was previously correct.
History
Date User Action Args
2014-12-23 23:16:53rhettingersetrecipients: + rhettinger, terry.reedy, ncoghlan, ezio.melotti, docs@python, IanLee1521
2014-12-23 23:16:53rhettingersetmessageid: <1419376613.71.0.869174523479.issue23061@psf.upfronthosting.co.za>
2014-12-23 23:16:53rhettingerlinkissue23061 messages
2014-12-23 23:16:53rhettingercreate