From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: "Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH] trace: avoid "is" with a literal Python 3.8 warnings
Date: Thu, 10 Oct 2019 16:02:57 +0200 [thread overview]
Message-ID: <98d5300a-537e-ff99-f79f-a177f4fd523b@redhat.com> (raw)
In-Reply-To: <20191010122154.10553-1-stefanha@redhat.com>
On 10/10/19 2:21 PM, Stefan Hajnoczi wrote:
> The following statement produces a SyntaxWarning with Python 3.8:
>
> if len(format) is 0:
> scripts/tracetool/__init__.py:459: SyntaxWarning: "is" with a literal. Did you mean "=="?
>
> Use the conventional len(x) == 0 syntax instead.
Ah this is a new change from 3.8...
https://docs.python.org/3.9/whatsnew/3.8.html
From https://bugs.python.org/issue34850
> Reported-by: Daniel P. Berrangé <berrange@redhat.com>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> scripts/tracetool/__init__.py | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/tracetool/__init__.py b/scripts/tracetool/__init__.py
> index 04279fa62e..44c118bc2a 100644
> --- a/scripts/tracetool/__init__.py
> +++ b/scripts/tracetool/__init__.py
> @@ -456,12 +456,12 @@ def generate(events, group, format, backends,
> import tracetool
>
> format = str(format)
> - if len(format) is 0:
> + if len(format) == 0:
> raise TracetoolError("format not set")
> if not tracetool.format.exists(format):
> raise TracetoolError("unknown format: %s" % format)
>
> - if len(backends) is 0:
> + if len(backends) == 0:
> raise TracetoolError("no backends specified")
> for backend in backends:
> if not tracetool.backend.exists(backend):
>
next prev parent reply other threads:[~2019-10-10 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 12:21 [PATCH] trace: avoid "is" with a literal Python 3.8 warnings Stefan Hajnoczi
2019-10-10 12:36 ` Daniel P. Berrangé
2019-10-10 14:02 ` Philippe Mathieu-Daudé [this message]
2019-10-10 16:13 ` Stefan Hajnoczi
2019-10-11 6:01 ` 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=98d5300a-537e-ff99-f79f-a177f4fd523b@redhat.com \
--to=philmd@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).