qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH] qapi: Fix some pycodestyle-3 complaints
Date: Thu, 21 Jun 2018 12:40:57 +0100	[thread overview]
Message-ID: <20180621114057.GI3615@redhat.com> (raw)
In-Reply-To: <877emso01o.fsf@dusky.pond.sub.org>

On Thu, Jun 21, 2018 at 01:23:47PM +0200, Markus Armbruster wrote:
> Daniel P. Berrangé <berrange@redhat.com> writes:
> 
> > On Thu, Jun 21, 2018 at 10:35:51AM +0200, Markus Armbruster wrote:
> >> Fix the following issues:
> >> 
> >>     common.py:873:13: E129 visually indented line with same indent as next logical line
> >>     common.py:1766:5: E741 ambiguous variable name 'l'
> >>     common.py:1784:1: E305 expected 2 blank lines after class or function definition, found 1
> >>     common.py:1833:1: E305 expected 2 blank lines after class or function definition, found 1
> >>     common.py:1843:1: E305 expected 2 blank lines after class or function definition, found 1
> >>     visit.py:181:18: E127 continuation line over-indented for visual indent
> >> 
> >> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> >> ---
> >>  scripts/qapi/common.py | 15 +++++++++------
> >>  scripts/qapi/visit.py  |  2 +-
> >>  2 files changed, 10 insertions(+), 7 deletions(-)
> >
> > Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> >
> >
> > If we care about pycodestyle-3 compliance, it is probably worth adding
> > that to 'make check' to avoid people introducing regressions.
> 
> It's not spotless, yet:
> 
> $ pycodestyle-3 scripts/qapi-gen.py scripts/qapi/*.py
> scripts/qapi/commands.py:66:80: E501 line too long (93 > 79 characters)
> scripts/qapi/common.py:818:49: E261 at least two spaces before inline comment
> scripts/qapi/visit.py:24:80: E501 line too long (86 > 79 characters)
> scripts/qapi/visit.py:117:80: E501 line too long (88 > 79 characters)
> scripts/qapi/visit.py:154:80: E501 line too long (87 > 79 characters)
> scripts/qapi/visit.py:167:80: E501 line too long (88 > 79 characters)
> scripts/qapi/visit.py:237:80: E501 line too long (88 > 79 characters)
> 
> The long lines are in mcgen() arguments.
> 
> If cleaning these up is the price for automation, I guess we'll pay it.

FWIW, --select=XXX or --ignore=XXX args let you turn off classes of warning
we don't wish to fix.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  reply	other threads:[~2018-06-21 11:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-21  8:35 [Qemu-devel] [PATCH] qapi: Fix some pycodestyle-3 complaints Markus Armbruster
2018-06-21  9:18 ` Daniel P. Berrangé
2018-06-21 11:23   ` Markus Armbruster
2018-06-21 11:40     ` Daniel P. Berrangé [this message]
2018-06-21 11:27 ` Markus Armbruster
2018-06-21 11:41   ` Daniel P. Berrangé
2018-06-21 11:40 ` Philippe Mathieu-Daudé
2018-07-09  7:07 ` Markus Armbruster

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=20180621114057.GI3615@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=mdroth@linux.vnet.ibm.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).