On Sat, Nov 30, 2013 at 11:36:53AM +0100, Joachim Durchholz wrote: > >Strict pep8 conformance may be distractive for newcommers, > Which is indeed a price to pay. > There's another price: Strict stylistic guidelines encourage bikeshedding.
Emm. Why so? > >the price is high: more merge conflicts, more noise in the git history, > > Eh? > Only if somebody insists on cleaning up pep8 warnings - not what > people do very often anyway. Well, may be I'm wrong - this is based on my personal expirience with git-blame. Actual example: $ git blame sympy/core/function.py|cut -f 1 -d" "|sort|uniq 229 $ git blame sympy/core/function.py|cut -f 1 -d" "|wc -l 2291 $ for c in `git blame sympy/core/function.py|cut -f 1 -d" "|sort|uniq`; do git show $c| egrep -iq '(pep8|pep 8)' && echo pep; done|wc -l 13 $ for c in `git blame sympy/core/function.py|cut -f 1 -d" "`; do git show $c| egrep -iq '(pep8|pep 8)' && echo pep; done|wc -l 145 -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. For more options, visit https://groups.google.com/groups/opt_out.
