qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: jsnow@redhat.com, armbru@redhat.com, peter.maydell@linaro.org,
	berrange@redhat.com
Subject: Re: [RFC PATCH 1/3] Python: Drop support for Python 3.7
Date: Mon, 4 Sep 2023 12:34:25 +0200	[thread overview]
Message-ID: <2fdf3391-bef5-7d86-d066-1f687cec1285@linaro.org> (raw)
In-Reply-To: <20230904095720.154738-2-pbonzini@redhat.com>

On 4/9/23 11:57, Paolo Bonzini wrote:
> Debian 10 is not anymore a supported distro, since Debian 12 was
> released on June 10, 2023.  Our supported build platforms as of today
> all support at least 3.8 (and all of them except for Ubuntu 20.04
> support 3.9):
> 
> openSUSE Leap 15.5: 3.6.15 (3.11.2)
> CentOS Stream 8:    3.6.8  (3.8.13, 3.9.16, 3.11.4)
> CentOS Stream 9:    3.9.17 (3.11.4)
> Fedora 37:          3.11.4
> Fedora 38:          3.11.4
> Debian 11:          3.9.2
> Debian 12:          3.11.2
> Alpine 3.14, 3.15:  3.9.16
> Alpine 3.16, 3.17:  3.10.10
> Ubuntu 20.04 LTS:   3.8.10
> Ubuntu 22.04 LTS:   3.10.12
> NetBSD 9.3:         3.9.13*
> FreeBSD 12.4:       3.9.16
> FreeBSD 13.1:       3.9.18
> OpenBSD 7.2:        3.9.17
> 
> Note: NetBSD does not appear to have a default meta-package, but offers
> several options, the lowest of which is 3.7.15. However, "python39"
> appears to be a pre-requisite to one of the other packages we request
> in tests/vm/netbsd.
> 
> Since it is safe to under our supported platform policy, bump our

Is 'under' a verb? This sentence is not obvious to me.

> minimum supported version of Python to 3.8.  The two most interesting
> features to have by default include:
> 
> - the importlib.metadata module, whose lack is responsible for over 100
>    lines of code in mkvenv.py
> 
> - improvements to asyncio, for example asyncio.CancelledError
>    inherits from BaseException rather than Exception
> 
> In addition, code can now use the assignment operator ':='
> 
> Because mypy now learns about importlib.metadata, a small change to
> mkvenv.py is needed to pass type checking.
> 
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
>   configure                | 8 ++++----
>   python/Makefile          | 8 ++++----
>   python/scripts/mkvenv.py | 5 ++++-
>   python/setup.cfg         | 7 +++----
>   python/tests/minreqs.txt | 2 +-
>   scripts/qapi/mypy.ini    | 2 +-
>   6 files changed, 17 insertions(+), 15 deletions(-)

Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>



  reply	other threads:[~2023-09-04 10:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04  9:57 [RFC PATCH 0/3] drop support for Python 3.7 and Debian 10 Paolo Bonzini
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é [this message]
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=2fdf3391-bef5-7d86-d066-1f687cec1285@linaro.org \
    --to=philmd@linaro.org \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=pbonzini@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).