From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org, "Daniel Berrangé" <berrange@redhat.com>
Cc: Cleber Rosa <crosa@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Michael Roth <michael.roth@amd.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [PULL 0/2] Python patches
Date: Wed, 20 Aug 2025 01:01:06 -0400 [thread overview]
Message-ID: <CAFn=p-bSh9kr2OOv0vq8H+quuUSww5NeV8LYBy2MKr-b82P2kA@mail.gmail.com> (raw)
In-Reply-To: <20250820045816.1142190-1-jsnow@redhat.com>
On Wed, Aug 20, 2025 at 12:58 AM John Snow <jsnow@redhat.com> wrote:
>
> The following changes since commit 5836af0783213b9355a6bbf85d9e6bc4c9c9363f:
>
> Merge tag 'uefi-20250812-pull-request' of https://gitlab.com/kraxel/qemu into staging (2025-08-13 15:19:29 -0400)
>
> are available in the Git repository at:
>
> https://gitlab.com/jsnow/qemu.git tags/python-pull-request
>
> for you to fetch changes up to 16398e73cd13c7d9f284d8ec4a440778fc2e3f9a:
>
> python: avoid deprecation warning with get_event_loop (2025-08-20 00:55:27 -0400)
>
> ----------------------------------------------------------------
> Python pull request
>
> Necessary for Python 3.14 support for iotests, releasing October 7th
>
> ----------------------------------------------------------------
>
> Daniel P. Berrangé (1):
> python: avoid deprecation warning with get_event_loop
>
> Richard W.M. Jones (1):
> python: Replace asyncio.get_event_loop for Python 3.14
>
> python/qemu/qmp/legacy.py | 10 +++++++++-
> python/qemu/qmp/qmp_tui.py | 2 +-
> python/tests/protocol.py | 2 +-
> 3 files changed, 11 insertions(+), 3 deletions(-)
>
> --
> 2.50.1
>
Dan: I wasn't sure if you were suggesting these to be pulled *right
away*, but just in case that is what you meant, I sent this PR for
what I think is the minimum necessary to avoid iotests croaking when
3.14 drops in October. Let me know if we need to make any other
adjustments here and I will follow up in the morning.
next prev parent reply other threads:[~2025-08-20 5:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 4:58 [PULL 0/2] Python patches John Snow
2025-08-20 4:58 ` [PULL 1/2] python: Replace asyncio.get_event_loop for Python 3.14 John Snow
2025-08-20 4:58 ` [PULL 2/2] python: avoid deprecation warning with get_event_loop John Snow
2025-08-20 5:01 ` John Snow [this message]
2025-08-20 13:33 ` [PULL 0/2] Python patches Daniel P. Berrangé
-- strict thread matches above, loose matches on Subject: below --
2023-02-23 4:36 John Snow
2023-02-24 15:07 ` Peter Maydell
2021-09-16 22:07 John Snow
2021-09-20 15: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='CAFn=p-bSh9kr2OOv0vq8H+quuUSww5NeV8LYBy2MKr-b82P2kA@mail.gmail.com' \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=michael.roth@amd.com \
--cc=peter.maydell@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).