Tres Seaver wrote:
- -1. The feature exists to allow adherence to PEP-8, Limit all lines to
a maximum of 79 characters., without requiring runtime concatenation
costs. I use it frequently when assembling and testing message strings,
for instance.
removing it is a bad idea for the reasons
On Sat, 23 Aug 2008, Fredrik Lundh wrote:
removing it is a bad idea for the reasons already given, but requiring
parentheses could help.
that is, the following would result in a warning or an error:
L = [first, second third]
but the following wouldn't:
L = [first, (second third)]
Isaac Morland wrote:
This would avoid accidentally leaving out commas in list construction,
but tuple construction would still have the same problem.
Tuple construction already has a no comma, no tuple problem. That
problem remains, but as soon as you add a comma, you'll get the same
when I'm trying to build extensions under Python 2.6 on Windows XP, the
build process terminates with single line that says:
error: None
which is about as useless as an error message can be. Googling for this
brings up a few hits which all seem to involve setuptools (and none of
the
Below are the problems I found that have not been fixed at r65995 on
trunk (2.6). There will be a separate mail for the 3.0 problems.
I've done the following:
* built in debug and opt mode (gcc 4.1.2) fixing the important warnings
* run all the tests in both modes
* run all the tests (except
