It's easy to only analyze the files in the diff (these linters don't do
cross-file analysis anyways, typically) and it's possible to write a filter
that only keeps warnings about lines that are changed, but I don't know of
a standard solution for the latter (places where I worked where I've seen
th
Can any of these said linters analyze only the diff in the PR, instead of
the entire CPython codebase?
Mariatta Wijaya
ᐧ
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.pyt
I'm not sure, I found the "with f(x) as y" form previously mentioned the most
readable despite it being a new use case, while not needing new keywords.
-Mike
On 2018-02-23 22:07, David Mertz wrote:
FWIW, the nested loop over a single item is already in the language for 15 years
or something.
On 24 February 2018 at 16:45, Barry Warsaw wrote:
> On Feb 21, 2018, at 19:03, Dan Stromberg wrote:
> >
> > Is flake8 that much better than pylint, that pylint wouldn't even be
> discussed?
>
> I honestly don’t use pylint all that much these days, but when I was
> evaluating them years ago, I fo
