From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: jsnow@redhat.com, armbru@redhat.com, peter.maydell@linaro.org,
berrange@redhat.com
Subject: [RFC PATCH 0/3] drop support for Python 3.7 and Debian 10
Date: Mon, 4 Sep 2023 11:57:17 +0200 [thread overview]
Message-ID: <20230904095720.154738-1-pbonzini@redhat.com> (raw)
Debian 10 is not anymore a supported distro, since Debian 12 was
released on June 10, 2023, and it is also the last distro that
supports Python 3.7.
Both Debian 10 and Python 3.7 required a substantial amount of
code in mkvenv.py, and John also mentioned that asyncio had changes
related to cancellation in Python 3.8. To start the discussion, here
is a first sample of cleanups that are enabled by supporting only Python
3.8 and newer.
Paolo
Paolo Bonzini (3):
Python: Drop support for Python 3.7
mkvenv: assume presence of importlib.metadata
Revert "mkvenv: work around broken pip installations on Debian 10"
configure | 8 +-
python/Makefile | 8 +-
python/scripts/mkvenv.py | 272 +++++++--------------------------------
python/setup.cfg | 16 +--
python/tests/minreqs.txt | 2 +-
scripts/qapi/mypy.ini | 2 +-
6 files changed, 59 insertions(+), 249 deletions(-)
--
2.41.0
next reply other threads:[~2023-09-04 9:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 9:57 Paolo Bonzini [this message]
2023-09-04 9:57 ` [RFC PATCH 1/3] Python: Drop support for Python 3.7 Paolo Bonzini
2023-09-04 10:34 ` Philippe Mathieu-Daudé
2023-09-05 6:00 ` Paolo Bonzini
2023-09-05 8:38 ` Philippe Mathieu-Daudé
2023-09-04 9:57 ` [RFC PATCH 2/3] mkvenv: assume presence of importlib.metadata Paolo Bonzini
2023-09-04 9:57 ` [RFC PATCH 3/3] Revert "mkvenv: work around broken pip installations on Debian 10" Paolo Bonzini
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=20230904095720.154738-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=jsnow@redhat.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).