➜

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 demian.brecht
Recipients BreamoreBoy, Matt.Spear, berker.peksag, demian.brecht, orsenthil
Date 2015-01-27.23:10:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <54C81AEE.9030108@gmail.com>
In-reply-to <1422399503.19.0.335348373877.issue13128@psf.upfronthosting.co.za>
Content 
Sure, I should have some time later today to do so.

Should such changes not be made as they're encountered in order to clean
up the older code that isn't up to spec? Or should they only be made as
the code is modified?

On 2015-01-27 2:58 PM, Berker Peksag wrote:
> 
> Berker Peksag added the comment:
> 
> Thanks for the patch! Could you revert unrelated changes (whitespaces, PEP 8 etc.) if you have time?
> 
> ----------
> stage: patch review -> commit review
> 
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue13128>
> _______________________________________
>
History
Date User Action Args
2015-01-27 23:10:44demian.brechtsetrecipients: + demian.brecht, orsenthil, BreamoreBoy, berker.peksag, Matt.Spear
2015-01-27 23:10:44demian.brechtlinkissue13128 messages
2015-01-27 23:10:44demian.brechtcreate