Re: [matplotlib-devel] PEP 8 change in Travis

[Paul I. <pi...@be...>]

Nelle Varoquaux, on 2014-03-26 21:27,  wrote:
> > Does anyone know why we are seeing a huge number of PEP 8 failures now?
> >   It looks to me like it is a change in which modules are subject to the
> > test, or in which tests are grounds for failure.  I don't know how all
> > this is set up, though.
> 
> If it started very recently, it could be linked to the new release. They
> have started to make "none backward" compatible version, in the sense that
> the stylechecker is increasingly strict. It is very annoying...

Can we not revisit (and possibly revert) the morally absolutist
PEP-8 or death position that matplotlib has taken?

Quoting GvR (emphasis mine):

    All I want to say is, people lighten up. The style guide
    can't solve all your problems. You are never going to have
    all code compliant. Use the style guide when it helps, *ignore
    it when it's in the way*

And from that same email:

    Let's try to make new stdlib modules use the best style we
    can think of, but limit the time spent fretting over code
    that's already there.
    

The rest of the message is useful to read:
https://mail.python.org/pipermail/python-dev/2010-November/105681.html

Another reason for not being so rigid about  PEP-8 is that its a
living document. Are we really doing massive search-and-replace
changes to the codebase just to comply with a moving target?

best,
-- 
                   _
                  / \
                A*   \^   -
             ,./   _.`\\ / \
            / ,--.S    \/   \
           /  `"~,_     \    \
     __o           ?
   _ \<,_         /:\
--(_)/-(_)----.../ | \
--------------.......J
Paul Ivanov
http://pirsquared.org