All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org, "Hanna Reitz" <hreitz@redhat.com>,
	"Kevin Wolf" <kwolf@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	qemu-block@nongnu.org,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Michael Roth" <michael.roth@amd.com>,
	"Cleber Rosa" <crosa@redhat.com>,
	"Beraldo Leal" <bleal@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 7/7] Python: Drop support for Python 3.6
Date: Thu, 9 Feb 2023 16:27:07 +0000	[thread overview]
Message-ID: <Y+Ue2/Xn+ZbOc+B+@redhat.com> (raw)
In-Reply-To: <20230209154034.983044-8-jsnow@redhat.com>

On Thu, Feb 09, 2023 at 10:40:34AM -0500, John Snow wrote:
> Python 3.6 was EOL 2021-12-31. Newer versions of upstream libraries have
> begun dropping support for this version and it is becoming more
> cumbersome to support. Avocado-framework and qemu.qmp each have their
> own reasons for wanting to drop Python 3.6.
>
> Since it is safe to under our supported platform policy, do so.

Upstream EOL dates are essentially irrelevant from our platform
support policy for deciding min versions

QEMU aims to target released OS distributions, and their vendors
may choose to support software for arbitrarily longer periods of
time than upstream. This extended support is one of the key
value adds of OS distributions.

To justify dropping python 3.6, the commit message needs to
illustrate that all our targetted distros are capable of
supporting the new proposed new min version. 

> 
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
>  docs/conf.py             |  4 ++--
>  configure                |  8 ++++----
>  python/Makefile          | 10 +++++-----
>  python/setup.cfg         |  7 +++----
>  python/tests/minreqs.txt |  2 +-
>  scripts/qapi/mypy.ini    |  2 +-
>  6 files changed, 16 insertions(+), 17 deletions(-)


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:[~2023-02-09 16:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09 15:40 [PATCH 0/7] Python: Drop support for Python 3.6 John Snow
2023-02-09 15:40 ` [PATCH 1/7] python: support pylint 2.16 John Snow
2023-02-09 16:01   ` Philippe Mathieu-Daudé
2023-02-09 17:49   ` Beraldo Leal
2023-02-09 15:40 ` [PATCH 2/7] Python: drop pipenv John Snow
2023-02-09 15:40 ` [PATCH 3/7] configure: Look for auxiliary Python installations John Snow
2023-02-10 19:45   ` Eric Blake
2023-02-15 20:10     ` John Snow
2023-02-09 15:40 ` [PATCH 4/7] configure: Add nice hint to Python failure message John Snow
2023-02-09 15:40 ` [PATCH 5/7] testing: Add Python >= 3.7 to Centos, OpenSuSE John Snow
2023-02-09 15:56   ` Thomas Huth
2023-02-09 16:10     ` John Snow
2023-02-10 10:38   ` Daniel P. Berrangé
2023-02-15 20:25     ` John Snow
2023-02-09 15:40 ` [PATCH 6/7] CI: Stop building docs on centos8 John Snow
2023-02-09 15:57   ` Thomas Huth
2023-02-09 16:05   ` Philippe Mathieu-Daudé
2023-02-09 22:43   ` Paolo Bonzini
2023-02-09 23:32     ` John Snow
2023-02-10 10:30       ` Paolo Bonzini
2023-02-15 20:31         ` John Snow
2023-02-09 15:40 ` [PATCH 7/7] Python: Drop support for Python 3.6 John Snow
2023-02-09 16:27   ` Daniel P. Berrangé [this message]
2023-02-09 16:40     ` John Snow
2023-02-09 18:03       ` Daniel P. Berrangé
2023-02-09 21:15         ` John Snow

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=Y+Ue2/Xn+ZbOc+B+@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=bleal@redhat.com \
    --cc=crosa@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=michael.roth@amd.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=wainersm@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.