Raymond Hettinger added the comment: Sorry, but I think many of these changes should not be made. Sometime the tight spacing is used for visual grouping. The following look fine and should not be changed because adding spaces around the + or * operator makes the whole sentence harder to mentally parse correctly: sum(x*y for x,y in zip(xvec, yvec)) a, b = b, a+b Also, it is perfectly correct to use: raise StopIteration We use the parentheses when there is an argument: raise KeyError('key not found: {!r}'.format(k)) Sometimes one-liners are okay in the interactive mode for quick filter functions and whatnot. Spreading them out with '...' lines makes the example harder to follow and expands the set-up part of the example rather than the part being explained. It's perfectly valid to use x * x * x instead of x**3 in an example of how to use map. We want the example to be as simple as possible. Also, the interactive prompt examples should be left as-is. They communicate the free-form nature of experimentation at the prompt. ---------- nosy: +rhettinger resolution: -> rejected status: open -> closed _______________________________________ Python tracker http://bugs.python.org/issue11425 _______________________________________

Éric Araujo added the comment: Just two notes: The operations like “7205759403792794 * 10**30 / 2**56” in floatimport could use some parens; the patch removed a duplicate “statement: for” entry. ---------- nosy: +eric.araujo _______________________________________ Python tracker http://bugs.python.org/issue11425 _______________________________________