-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
One can make it pass with the very ugly:
somemodule.chaining.there(p='foo', anotherpara=('value which can potentially' 'be super long'))
Yes this IS VERY UGLY.
Or putting each parameter on each on line:
somemodule.longmethod.chaining.there( p='foo', anotherpara=('value which can potentially be super long'))
UGLY too. At least the first parameter should be allowed to be on the first line.
That specific E128 code can be ignored with a .pep8 file containing:
[pep8] # This is a commented out line # E128 continuation line under-indented for visual indent ignore = E128
So once you experimented pep8 annoyance, you can selectively get rid of some checks :-]
As I mentioned - IMHO I would start by ignoring everything that our code does not pass at the moment and then starting to improve the code and successively remove ignores whenever possible. The most important style checks are already done or enforced by the python interpreter. (rember the differences between python and e.g. perl)
Also I would like to remember:
http://www.mediawiki.org/wiki/Gerrit/Code_review#Goals
"Tolerate idiosyncrasies where possible. Developers should feel that their creative input is valued and preserved."
Sometimes it's just not possible to decide which style is the better one and I am always intressted in seeing other styles also in order to learn something new (may be better ;) - and avoid to get bored. But of course pep8 is always good for orientation and as "how it SHOULD be".
Greetings to all! DrTrigon