qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>,
	Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [PATCH] iotests/297: pylint: ignore too many statements
Date: Fri, 29 Jan 2021 12:57:02 -0500	[thread overview]
Message-ID: <d090331e-33d7-925d-e59e-420e9a39a5a2@redhat.com> (raw)
In-Reply-To: <20210129095018.GB10888@merkur.fritz.box>

On 1/29/21 4:50 AM, Kevin Wolf wrote:
> Am 28.01.2021 um 21:08 hat Vladimir Sementsov-Ogievskiy geschrieben:
>> 28.01.2021 23:04, Vladimir Sementsov-Ogievskiy wrote:
>>> Ignore two complains, which now lead to 297 failure on testenv.py and
>>> testrunner.py.
>>>
>>> Fixes: 2e5a2f57db481f18fcf70be2a36b1417370b8476
>>> Fixes: d74c754c924ca34e90b7c96ce2f5609d82c0e628
>>> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
>>> ---
>>
>> Forget to note:
>>
>> I don't add exclusions to pylintrc intentionally, as I think these
>> warnings are reasonable, and it's good that vim ALE show them.. Still,
>> adding them to pylintrc works too if you prefer.
> 
> I would have disabled the warning completely because I don't think
> length in lines is a good measure for code quality. But if we think that
> these warnings are in fact reasonable, then we should fix them and not
> just disable them partially.
> 
> It's the same reason why we have -Werror enabled. If you leave warnings
> around without any intention to fix them, the useful warnings will drown
> in the masses of intentionally ignored ones.
> 
> Kevin
> 

It's at least a sniff test. There are extremely valid reasons for many 
of the "warnings" to be suppressed, but usually you should have to 
consciously justify it, I think.

Vladimir put the suppression in pylintrc under the "Temporary" section 
for v2, which I think is appropriate, so I gave it my R-B.

--js



      reply	other threads:[~2021-01-29 17:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28 20:04 [PATCH] iotests/297: pylint: ignore too many statements Vladimir Sementsov-Ogievskiy
2021-01-28 20:08 ` Vladimir Sementsov-Ogievskiy
2021-01-29  9:50   ` Kevin Wolf
2021-01-29 17:57     ` John Snow [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d090331e-33d7-925d-e59e-420e9a39a5a2@redhat.com \
    --to=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@virtuozzo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).