qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
	"John Snow" <jsnow@redhat.com>, "Cleber Rosa" <crosa@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH] tests, scripts: Don't import print_function from __future__
Date: Tue, 19 Aug 2025 12:30:01 +0100	[thread overview]
Message-ID: <aKRgObageF20y5Xm@redhat.com> (raw)
In-Reply-To: <20250819102409.2117969-1-peter.maydell@linaro.org>

On Tue, Aug 19, 2025 at 11:24:09AM +0100, Peter Maydell wrote:
> Some of our Python scripts still include the line
>   from __future__ import print_function
> 
> which is intended to allow a Python 2 to handle the Python 3 print()
> syntax. This particular part of the future arrived many years ago,
> and our minimum Python version is 3.9, so we don't need to keep
> this line around.
> 
> NB: the scripts in tests/tcg/*/gdbstub/ are run with whatever Python
> gdb was built against, but we can safely assume that that was a
> Python 3 because our supported distros are all on Python 3.  In any
> case these are only run as part of "make check-tcg", not by
> end-users.
> 
> Commit created with:
> 
>  sed -i -e '/import print_function/d' $(git grep -l 'from __future__')
> 
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
>  scripts/userfaultfd-wrlat.py                           | 1 -
>  tests/guest-debug/test_gdbstub.py                      | 1 -
>  tests/tcg/aarch64/gdbstub/test-mte.py                  | 1 -
>  tests/tcg/aarch64/gdbstub/test-sve-ioctl.py            | 1 -
>  tests/tcg/aarch64/gdbstub/test-sve.py                  | 1 -
>  tests/tcg/multiarch/gdbstub/interrupt.py               | 1 -
>  tests/tcg/multiarch/gdbstub/memory.py                  | 1 -
>  tests/tcg/multiarch/gdbstub/sha1.py                    | 1 -
>  tests/tcg/multiarch/gdbstub/test-proc-mappings.py      | 1 -
>  tests/tcg/multiarch/gdbstub/test-qxfer-auxv-read.py    | 1 -
>  tests/tcg/multiarch/gdbstub/test-qxfer-siginfo-read.py | 1 -
>  tests/tcg/multiarch/gdbstub/test-thread-breakpoint.py  | 1 -
>  tests/tcg/s390x/gdbstub/test-signals-s390x.py          | 1 -
>  tests/tcg/s390x/gdbstub/test-svc.py                    | 1 -
>  14 files changed, 14 deletions(-)

Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>


With 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:[~2025-08-19 11:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-19 10:24 [PATCH] tests, scripts: Don't import print_function from __future__ Peter Maydell
2025-08-19 11:30 ` Daniel P. Berrangé [this message]
2025-08-19 21:30 ` John Snow
2025-08-20  6:34 ` Philippe Mathieu-Daudé
2025-09-01 16:16 ` Peter Maydell

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=aKRgObageF20y5Xm@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=crosa@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --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).