From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Eduardo Habkost" <ehabkost@redhat.com>,
qemu-devel@nongnu.org, "John Snow" <jsnow@redhat.com>,
"Michael Roth" <mdroth@linux.vnet.ibm.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: Python 3.5 EOL; when can require 3.6?
Date: Wed, 16 Sep 2020 14:53:55 +0100 [thread overview]
Message-ID: <87d02lzv2k.fsf@linaro.org> (raw)
In-Reply-To: <436800a3-7645-52f7-5fea-134d883c0a7b@redhat.com>
Thomas Huth <thuth@redhat.com> writes:
> On 16/09/2020 09.53, Philippe Mathieu-Daudé wrote:
>> On 9/16/20 9:43 AM, Markus Armbruster wrote:
>>> We require Python 3.5. It will reach its "end of life" at the end of
>>> September 2020[*]. Any reason not to require 3.6 for 5.2? qemu-iotests
>>> already does for its Python parts.
>>>
>>>
>>> [*] https://www.python.org/downloads/release/python-3510/
>>
>> Not answering your question, but it would help to start a table
>> of "oldest package released" versions, with our supported distributions
>> as columns and package names as row.
>>
>> This way when new distributions are released (and oldest dropped from
>> our side) we can add/remove a column and see the oldest version we aim
>> to support.
>
> That's quite a bit of extra work - I think it's enough to look up the
> versions on repology instead, e.g.:
>
> https://repology.org/project/python/versions
Hmm are there any magic runes to limit the list to only the distros we
care about?
--
Alex Bennée
next prev parent reply other threads:[~2020-09-16 13:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 7:43 Python 3.5 EOL; when can require 3.6? Markus Armbruster
2020-09-16 7:53 ` Philippe Mathieu-Daudé
2020-09-16 8:02 ` Thomas Huth
2020-09-16 8:16 ` Philippe Mathieu-Daudé
2020-09-16 13:53 ` Alex Bennée [this message]
2020-09-16 13:57 ` Daniel P. Berrangé
2020-09-17 14:53 ` Eduardo Habkost
2020-09-16 8:22 ` Andrea Bolognani
2020-09-16 15:09 ` Eduardo Habkost
2020-09-16 7:54 ` Thomas Huth
2020-09-16 8:33 ` Daniel P. Berrangé
2020-09-16 9:50 ` Thomas Huth
2020-09-16 9:54 ` Daniel P. Berrangé
2020-09-16 9:55 ` Thomas Huth
2020-09-16 8:31 ` Daniel P. Berrangé
2020-09-16 12:30 ` Peter Maydell
2020-09-16 13:30 ` Markus Armbruster
2020-09-16 14:00 ` Thomas Huth
2020-09-16 14:05 ` Daniel P. Berrangé
2020-09-16 14:57 ` John Snow
2020-09-17 14:10 ` Thomas Huth
2020-09-17 14:55 ` Daniel P. Berrangé
2020-09-17 15:24 ` Thomas Huth
2020-09-17 15:39 ` Daniel P. Berrangé
2020-09-17 15:41 ` Thomas Huth
2020-09-17 15:30 ` Markus Armbruster
2020-09-17 15:39 ` Thomas Huth
2020-09-17 15:42 ` Warner Losh
2020-09-17 16:07 ` Andrea Bolognani
2020-09-17 16:35 ` Daniel P. Berrangé
2020-09-17 17:02 ` Andrea Bolognani
2020-09-17 16:19 ` Eduardo Habkost
2020-09-17 16:33 ` Daniel P. Berrangé
2020-09-17 16:50 ` Eduardo Habkost
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=87d02lzv2k.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jsnow@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@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.