<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 11/22/14 4:02 AM, Kay Hayen wrote:<br>
</div>
<blockquote
cite="mid:CAMEZBDKFfzk_nfOZ4_Jg0A=KVZEk5yPS8KxxhuuOBKpURdthJw@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div>Hello there,</div>
<div><br>
</div>
<div>I have deployed that, in my check-with-pylint on the
factory git branch, I am now</div>
<div>for the first time ever, in Nuitka, fully pylint clean with
PyLint1.3.</div>
<div><br>
</div>
<div>What that message above does, is to make PyLint very
version dependent. There are new messages to that version, and
there are fixed false alarms and new false alarms. But there
is no way around that, right?</div>
<div><br>
</div>
<div>As a tool for distributed development, that's not ideal.
Say I would want to make these checks part of commit hooks, I
would require people to have 1.3 somewhere, when they already
have 1.4, or still 1.2, you get the idea.<br>
</div>
</div>
</blockquote>
Wouldn't you pin the version of PyLint in your requirements.txt
file?<br>
<blockquote
cite="mid:CAMEZBDKFfzk_nfOZ4_Jg0A=KVZEk5yPS8KxxhuuOBKpURdthJw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div>Or do I still get to implement the "delta of PyLint
warnings didn't worsen" check for that commit hook, even
though I am supposedly now PyLint clean. Seems there is no
real way around that?</div>
</div>
</blockquote>
BTW, diff-cover is a tool that can give you coverage, pep8, and
pylint measurements just for your changes, rather than for the
entire source tree that results from your changes. It's a good way
to focus developers on improving quality metrics.<br>
<br>
--Ned.<br>
<blockquote
cite="mid:CAMEZBDKFfzk_nfOZ4_Jg0A=KVZEk5yPS8KxxhuuOBKpURdthJw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div>Yours,</div>
<div>Kay</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2014-11-21 23:12 GMT+01:00 Torsten
Marek <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:shlomme@gmail.com" target="_blank">shlomme@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Yes, I0021 is useless-suppression.
<div><br>
</div>
<div>There's also suppressed-message, to show what kinds
of messages have been suppressed. Looking at that every
once in a while is interesting as well. Especially for
badly understood messages, there is a tendency in
developers to just paper over the warnings instead of
fixing the underlying issue.</div>
<span class="HOEnZb"><font color="#888888">
<div><br>
</div>
<div>// Torsten</div>
</font></span></div>
<div class="HOEnZb">
<div class="h5">
<div class="gmail_extra"><br>
<div class="gmail_quote">2014-11-21 18:32 GMT+01:00
Anne Mulhern <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:amulhern@redhat.com"
target="_blank">amulhern@redhat.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div><br>
<br>
<br>
<br>
----- Original Message -----<br>
> From: "Kay Hayen" <<a
moz-do-not-send="true"
href="mailto:kay.hayen@gmail.com"
target="_blank">kay.hayen@gmail.com</a>><br>
> To: <a moz-do-not-send="true"
href="mailto:code-quality@python.org"
target="_blank">code-quality@python.org</a><br>
> Sent: Wednesday, October 29, 2014
10:00:15 AM<br>
> Subject: [code-quality] How to detect
unused PyLint declarations<br>
><br>
><br>
> Hello,<br>
><br>
> I have coding rules that require me to
annotate exceptions to rules<br>
> for PyLint, but occasionally it happens
that I find PyLint rules disabled<br>
> that would no longer be necessary.<br>
><br>
> Is there a way or script, or anything to
detect these automatically? I<br>
> was thinking of writing something that
removes PyLint disablers one<br>
> by one, and checks if that doesn't
generate PyLint warnings, and<br>
> warn about those. Didn't do it so far,
but I feel tempted to do this<br>
> now.<br>
><br>
> However, to PyLint, this might be way
more easier to implement, and<br>
> maybe it was done. I cannot find anything
in the manpage though.<br>
><br>
> Yours,<br>
> Kay<br>
><br>
</div>
</div>
<span>>
_______________________________________________<br>
> code-quality mailing list<br>
> <a moz-do-not-send="true"
href="mailto:code-quality@python.org"
target="_blank">code-quality@python.org</a><br>
> <a moz-do-not-send="true"
href="https://mail.python.org/mailman/listinfo/code-quality"
target="_blank">https://mail.python.org/mailman/listinfo/code-quality</a><br>
><br>
<br>
</span>This is something I am interested in as
well.<br>
<br>
It looks like the I0021: Useless suppression of %s
warning<br>
should report those cases.<br>
<span><font color="#888888"><br>
- mulhern<br>
</font></span>
<div>
<div>_______________________________________________<br>
code-quality mailing list<br>
<a moz-do-not-send="true"
href="mailto:code-quality@python.org"
target="_blank">code-quality@python.org</a><br>
<a moz-do-not-send="true"
href="https://mail.python.org/mailman/listinfo/code-quality"
target="_blank">https://mail.python.org/mailman/listinfo/code-quality</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
code-quality mailing list
<a class="moz-txt-link-abbreviated" href="mailto:code-quality@python.org">code-quality@python.org</a>
<a class="moz-txt-link-freetext" href="https://mail.python.org/mailman/listinfo/code-quality">https://mail.python.org/mailman/listinfo/code-quality</a>
</pre>
</blockquote>
<br>
</body>
</html>