From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Jan Beulich <jbeulich@suse.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 13:04:32 +0100 [thread overview]
Message-ID: <ZBRXUOvzRQOk9NOA@mail-itl> (raw)
In-Reply-To: <afe67927-0f62-511b-012f-2f2deedbf4e6@suse.com>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
On Fri, Mar 17, 2023 at 09:46:33AM +0100, Jan Beulich wrote:
> 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.
Hmm, in fact the only part of this series that isn't python2 compatible
anymore is "install-python-bindings" target in tools/libs/stat/Makefile.
And it's enabled only with XENSTAT_PYTHON_BINDING=y is explicitly set.
So, maybe this readme change isn't relevant at all, at least not yet.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-03-17 12:05 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
2023-03-17 12:04 ` Marek Marczykowski-Górecki [this message]
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=ZBRXUOvzRQOk9NOA@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--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.