From: John Snow <jsnow@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Kevin Wolf <kwolf@redhat.com>
Cc: den@openvz.org, qemu-devel@nongnu.org, qemu-block@nongnu.org,
mreitz@redhat.com
Subject: Re: [PATCH v9 0/6] Rework iotests/check
Date: Mon, 15 Feb 2021 20:49:31 -0500 [thread overview]
Message-ID: <af46aebd-a6b4-cc64-1d6e-d08e78c6b0ae@redhat.com> (raw)
In-Reply-To: <5bb6d3fd-2a2c-91a4-f12a-5e195627a7fb@virtuozzo.com>
On 1/26/21 10:15 AM, Vladimir Sementsov-Ogievskiy wrote:
>>
>
> OK, thanks for handling it!
>
> When will we move to python 3.7?
"I don't know, but it seems like a very long time."
The nominal EOL for Python 3.6 is this December; see
https://www.python.org/dev/peps/pep-0494/
Debian 10 ships 3.7.
Fedora has appropriate packages going back to F29 and possibly earlier.
OpenSuSE tumbleweed offers 3.8 and 3.9.
Ubuntu 18.04 LTS offers 3.7 and 3.8 packages.
Ubuntu 20.04 LTS offers 3.7 and 3.8 packages.
OpenSUSE 15.2 ... ships with Python 3.6, and I don't see an option to
install anything more modern. This distribution is supported (both by us
and by SuSE) until 2021-12-31.
As of 2020-12-29, OpenSuSE 15.3 appears to be set to ship Python 3.6:
"python3-3.6.12-3.70.1.x86_64.rpm". It is set to ship 2021-07-07, and
does not have an estimated EOL date yet.
SLES 15 ... I'm not sure and can't seem to find that information
quickly. https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15-SP1/
which was published at the end of 2020, suggests that Python 3
support(?) is new(?) to some extent.
https://packagehub.suse.com/packages/python3/ suggests that SLES 15.2 is
Python 3.6-based.
I can't tell if they offer the optional addition of Python 3.7 on either
SLES or OpenSuSE. Would love to know.
As for RHEL/CentOS, I think it's in the same shape right now. It's
3.6-based, but I don't know if there's an optional 3.7+ package or not.
--js
Note: our configure script doesn't try several canonical sources of
Python interpreters, we just try to use "python3". In the case of
multiple python installations, we'd have to try python3.7, python3.8,
python3.9, etc.
next prev parent reply other threads:[~2021-02-16 1:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 18:50 [PATCH v9 0/6] Rework iotests/check Vladimir Sementsov-Ogievskiy
2021-01-25 18:50 ` [PATCH v9 1/6] iotests: 146: drop extra whitespaces from .out file Vladimir Sementsov-Ogievskiy
2021-01-27 18:22 ` Eric Blake
2021-01-25 18:50 ` [PATCH v9 2/6] iotests: add findtests.py Vladimir Sementsov-Ogievskiy
2021-01-25 18:50 ` [PATCH v9 3/6] iotests: add testenv.py Vladimir Sementsov-Ogievskiy
2021-01-26 10:10 ` Vladimir Sementsov-Ogievskiy
2021-01-25 18:50 ` [PATCH v9 4/6] iotests: add testrunner.py Vladimir Sementsov-Ogievskiy
2021-01-26 10:11 ` Vladimir Sementsov-Ogievskiy
2021-01-25 18:50 ` [PATCH v9 5/6] iotests: rewrite check into python Vladimir Sementsov-Ogievskiy
2021-01-25 18:50 ` [PATCH v9 6/6] iotests: rename and move 169 and 199 tests Vladimir Sementsov-Ogievskiy
2021-02-02 15:57 ` Daniel P. Berrangé
2021-02-02 16:15 ` Vladimir Sementsov-Ogievskiy
2021-01-26 12:53 ` [PATCH v9 0/6] Rework iotests/check Kevin Wolf
2021-01-26 13:19 ` Vladimir Sementsov-Ogievskiy
2021-01-26 13:29 ` Kevin Wolf
2021-01-26 15:07 ` Kevin Wolf
2021-01-26 15:15 ` Vladimir Sementsov-Ogievskiy
2021-01-26 15:36 ` Kevin Wolf
2021-01-26 15:52 ` Vladimir Sementsov-Ogievskiy
2021-02-16 1:49 ` John Snow [this message]
2021-02-16 13:03 ` Thomas Huth
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=af46aebd-a6b4-cc64-1d6e-d08e78c6b0ae@redhat.com \
--to=jsnow@redhat.com \
--cc=den@openvz.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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 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).