Hello Stephen,
> > But I assume,
> > you don't care about people who still care about Python2 code
> > correctness and Python3 correctness at the same time? It
> > must be a clear minority that I am in.
>
> Hey, I'm finally in a minority. I have a code base that has to remain
> in Python 2, too.
Hello there,
so I have added PyLint checks to travis. It nicely makes sure that PRs
I get submitted become clean.
However, for each PyLint release, e.g. 2.0.0, there will be a bunch of
findings that are new, and will to be found, leading to the Travis
builds to fail due to PyLint, all the time no
Hey,
On Tue, Jul 17, 2018 at 09:38:13AM +0200, Kay Hayen wrote:
> However, for each PyLint release, e.g. 2.0.0, there will be a bunch of
> findings that are new, and will to be found, leading to the Travis
> builds to fail due to PyLint, all the time now.
>
> How to approach that. Is there a way
Hi,
Another alternative would be to pin pylint for now to 1.9
so that it works out of the box for both Python 2 and 3. Also
forgot to mention that we have plans to add support of linting
Python 2 files while the running interpreter is Python 3
but we didn't have enough time before release to imple
Hello Claudiu,
> Also
> forgot to mention that we have plans to add support of linting
> Python 2 files while the running interpreter is Python 3
> but we didn't have enough time before release to implement
> that: https://github.com/PyCQA/pylint/issues/2070. Once
> we have that feature, you can j
