From: John Snow <jsnow@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Daniel Berrange <berrange@redhat.com>
Subject: python qemu.qmp v0.0.3 released
Date: Mon, 10 Jul 2023 14:03:51 -0400 [thread overview]
Message-ID: <CAFn=p-bgqcMWB3h0bEy2H9zC8sTV1UEov=i430sVaMLKoVQgEw@mail.gmail.com> (raw)
Hi all, I've just published qemu.qmp v0.0.3 to PyPI.
PyPI: https://pypi.org/project/qemu.qmp/0.0.3/
readthedocs: https://qemu.readthedocs.io/projects/python-qemu-qmp/en/latest/
changelog: https://qemu.readthedocs.io/projects/python-qemu-qmp/en/latest/main.html#changelog
Notably, this release drops support for Python 3.6 and modernizes the
python packaging infrastructure to be compatible with the forthcoming
Python 3.12 release expected this October. There is no impact to the
QEMU codebase at this time which is still using a wholly vendored
version of the library (that we dropped 3.6 support from earlier this
development cycle.)
Thanks,
--js
reply other threads:[~2023-07-10 18:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-bgqcMWB3h0bEy2H9zC8sTV1UEov=i430sVaMLKoVQgEw@mail.gmail.com' \
--to=jsnow@redhat.com \
--cc=berrange@redhat.com \
--cc=pbonzini@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).