[issue11929] Improve usage of PEP8 in Docs/includes/*

2011-04-26 Thread Roundup Robot
Roundup Robot added the comment: New changeset 5e93c5cdc378 by Raymond Hettinger in branch '3.2': Issue 11929: Minor whitespace clean-ups. http://hg.python.org/cpython/rev/5e93c5cdc378 New changeset 89fcadbc49df by Raymond Hettinger in branch 'default': Issue 11929: Minor whitespace clean-ups.

[issue11929] Improve usage of PEP8 in Docs/includes/*

2011-04-26 Thread Raymond Hettinger
Raymond Hettinger added the comment: I put a few of these in (ones where it looked like readability was improved). -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue11929] Improve usage of PEP8 in Docs/includes/*

2011-04-26 Thread Raymond Hettinger
Raymond Hettinger added the comment: > foo(x=default) vs. foo(x = default) That's fine. Most of the rest of it isn't. -- ___ Python tracker ___ ___

[issue11929] Improve usage of PEP8 in Docs/includes/*

2011-04-26 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: On the other hand, I would be +0 for the tzinfo-examples fixes of the form: foo(x=default) vs. foo(x = default) (This was also the fix suggested on the ML.) Overall, I think it is good to judicially point out to PEP 8 violations where fixes would impro

[issue11929] Improve usage of PEP8 in Docs/includes/*

2011-04-26 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Another -1 from me. Similar changes to inline examples in the docs have been rejected in the past for the same reasons as Raymond wrote. See issue 4649. -- nosy: +belopolsky ___ Python tracker

[issue11929] Improve usage of PEP8 in Docs/includes/*

2011-04-26 Thread Raymond Hettinger
Changes by Raymond Hettinger : -- assignee: docs@python -> rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue11929] Improve usage of PEP8 in Docs/includes/*

2011-04-26 Thread Raymond Hettinger
Raymond Hettinger added the comment: IMO, this is a complete waste of time and much of the code doesn't actually read any better afterwards. Some of the mathematical expressions look worse. There may be some merit to splitting the imports but that isn't worth much either, perhaps not enough

[issue11929] Improve usage of PEP8 in Docs/includes/*

2011-04-26 Thread Sandro Tosi
New submission from Sandro Tosi : Following up http://mail.python.org/pipermail/docs/2011-April/004032.html I made a run of pep8 on Doc/includes/ py files. i've prepared a patch against default; if it's considered worth I can prepare patches for the other branches (for sure 2.7 needs a differe