> because pep8 is pep8

But pep8 isn't PEP 8, in which I can't find anything about this
whitespace-between-comma-and-end-of-list rule.

And PEP8 is also under-specific for cases like the line below where a
series of function calls are stacked (`.sum().min()`), and go over the line
limit; I think putting the line break between the `.` and the `min` is a
bit weird, but the only thing PEP8 says that may come to bear here is "The
preferred place to break around a binary operator is *after* the operator,
not before it.", and then gives examples of 'and', 'or' and '%' which are
to be surrounded by whitespace anyway.

Finally, pep8 completely disregards PEP 8's requirement that comments and
docstrings should be wrapped to 72 characters. As does scikit-learn.


On 19 January 2014 01:25, Gael Varoquaux <notifications@github.com> wrote:

>  In sklearn/cluster/bicluster/__init__.py:
>
> > @@ -1,4 +1,4 @@
> >  from .spectral import SpectralCoclustering, SpectralBiclustering
> >
> >  __all__ = ['SpectralCoclustering',
> > -           'SpectralBiclustering',]
> > +           'SpectralBiclustering', ]
>
> I would prefer the new line, but this version is better than the previous,
> because pep8 is pep8, and we shouldn't argue with it (it's a bit like speed
> limits on highways :P )
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/scikit-learn/scikit-learn/pull/2763/files#r8987877>
> .
>