Hello PyLint team,
my congratulations too. I have a few questions though.
First of all, I am going to maintain my code base for Python2 and
Python3 dual lingo. Using both the Python2 and the Python3 variant of
PyLint, in different major versions poses a problem.
One thing I encounter is "too-man
Hi Kay,
On 16 July 2018 at 13:56, Kay Hayen wrote:
> Hello PyLint team,
>
> my congratulations too. I have a few questions though.
Thank you!
>
> First of all, I am going to maintain my code base for Python2 and
> Python3 dual lingo. Using both the Python2 and the Python3 variant of
> PyLint,
Hello there,
> > disable=too-many-statements, but say pylint2:
> > disable=too-many-statements
> > and then only that "pylint2" version would consider it. But I assume,
> > you don't care about people who still care about Python2 code
> > correctness and Python3 correctness at the same time? It
>
On 07/16/2018 04:56 AM, Kay Hayen wrote:
> 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 Pyt
Hi Federico,
This looks like an interesting plugin - thanks for sharing! It's great to see
tools that aim to improve the quality of tests (over and above regular linting).
Personally, I've moved away from Unittest to pytest so this plugin is not so
relevant for my usual testing work. __But__ (a
