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 implement that: https://github.com/PyCQA/pylint/issues/2070. Once we have that feature, you can just have pylint 2.X installed and run it for both Python 2 and 3 linting. On 17 July 2018 at 09:32, Kay Hayen <kay.hayen@gmail.com> wrote:
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. The issue is included code (via PIP) which isn't Python-3 safe yet.
But to be really in the minority, you have to run your code in Python2 and Python3 both.
And running PyLint for only Python3 wouldn't cut it, because testing for Python2 regressions would burn through massive amounts of CPU.
I am almost thinking, that minority is just me. :)
Yours, Kay _______________________________________________ code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality