From: Jan Beulich <jbeulich@suse.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 4/4] Update README to state Python3 requirement
Date: Fri, 17 Mar 2023 09:46:33 +0100 [thread overview]
Message-ID: <afe67927-0f62-511b-012f-2f2deedbf4e6@suse.com> (raw)
In-Reply-To: <20230316171634.320626-4-marmarek@invisiblethingslab.com>
On 16.03.2023 18:16, Marek Marczykowski-Górecki wrote:
> Python2 is not supported anymore.
There are two things here which concern me: For one, how come this is
at the end of a series? You want to keep in mind that any series may
be committed piecemeal (unless an indication to the contrary is in
the cover letter, but there's none here in the first place).
The other aspect is that there's no indication here of it being
consensus that we raise the baseline requirement for Python, and for
Python alone. A decision towards the wider topic of raising baseline
requirements is, as you may recall from the meeting in Cambridge,
still pending.
Jan
next prev parent reply other threads:[~2023-03-17 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 17:16 [PATCH 1/4] tools: convert setup.py to use setuptools Marek Marczykowski-Górecki
2023-03-16 17:16 ` [PATCH 2/4] tools: don't use distutils in configure nor Makefile Marek Marczykowski-Górecki
2023-03-16 17:16 ` [PATCH 3/4] tools: regenerate configure Marek Marczykowski-Górecki
2023-03-16 17:16 ` [PATCH 4/4] Update README to state Python3 requirement Marek Marczykowski-Górecki
2023-03-17 8:46 ` Jan Beulich [this message]
2023-03-17 12:04 ` Marek Marczykowski-Górecki
2023-03-17 12:37 ` George Dunlap
2023-03-17 14:54 ` Jan Beulich
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=afe67927-0f62-511b-012f-2f2deedbf4e6@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=julien@xen.org \
--cc=marmarek@invisiblethingslab.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 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.