From: John Snow <jsnow@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: crosa@redhat.com, philmd@redhat.com, qemu-devel@nongnu.org,
ehabkost@redhat.com, mdroth@linux.vnet.ibm.com
Subject: Re: [PATCH v2 4/4] qapi: Brush off some (py)lint
Date: Thu, 5 Mar 2020 13:09:44 -0500 [thread overview]
Message-ID: <0f4f70fe-238d-0d8e-72e5-796db9d601fa@redhat.com> (raw)
In-Reply-To: <87blpb1h1i.fsf@dusky.pond.sub.org>
On 3/5/20 12:56 AM, Markus Armbruster wrote:
> John Snow <jsnow@redhat.com> writes:
>
>> On 3/4/20 10:59 AM, Markus Armbruster wrote:
>>> Signed-off-by: Markus Armbruster <armbru@redhat.com>
>>> ---
>>> scripts/qapi/commands.py | 2 +-
>>> scripts/qapi/expr.py | 3 +--
>>> scripts/qapi/gen.py | 9 ++++++---
>>> scripts/qapi/introspect.py | 2 --
>>> scripts/qapi/parser.py | 6 ++----
>>> scripts/qapi/schema.py | 11 +++++------
>>> 6 files changed, 15 insertions(+), 18 deletions(-)
>>>
>>
>> Looks okay. (I don't care as much about no-else-return being there or
>> not, and this module is your baby.)
>
> I admit I personally prefer to elide the else there. But my main
> argument is consistent style. Picking the one pylint wants makes
> consistency easier.
>
>> Reviewed-by: John Snow <jsnow@redhat.com>
>
> Thanks!
>
I capitulated to Max and Kevin who disliked the same, and also
personally agree I like to visually see the branches.
(If we want a tree-wide python style it might be useful to converge the
linting configurations at some point -- but not yet, and it's not as
important as the more nuts and bolts cleanups to remove Python3. RB
stands, of course.)
--js
prev parent reply other threads:[~2020-03-05 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 15:59 [PATCH v2 0/4] qapi: Bye-bye Python 2 Markus Armbruster
2020-03-04 15:59 ` [PATCH v2 1/4] qapi: Inheriting from object is pointless with Python 3, drop Markus Armbruster
2020-03-04 20:25 ` John Snow
2020-03-04 15:59 ` [PATCH v2 2/4] qapi: Drop conditionals for Python 2 Markus Armbruster
2020-03-04 20:26 ` John Snow
2020-03-04 15:59 ` [PATCH v2 3/4] qapi: Use super() now we have Python 3 Markus Armbruster
2020-03-04 20:30 ` John Snow
2020-03-04 15:59 ` [PATCH v2 4/4] qapi: Brush off some (py)lint Markus Armbruster
2020-03-04 20:33 ` John Snow
2020-03-05 5:56 ` Markus Armbruster
2020-03-05 18:09 ` 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=0f4f70fe-238d-0d8e-72e5-796db9d601fa@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).