From: Anthony PERARD <anthony.perard@citrix.com>
To: Wei Liu <wl@xen.org>
Cc: xen-devel@lists.xenproject.org,
Ian Jackson <ian.jackson@eu.citrix.com>,
Doug Goldstein <cardoe@cardoe.com>
Subject: Re: [Xen-devel] [XEN PATCH 0/3] Default to python3
Date: Mon, 27 Jan 2020 12:36:23 +0000 [thread overview]
Message-ID: <20200127123623.GL1288@perard.uk.xensource.com> (raw)
In-Reply-To: <20200127123021.gqxdbe2vv4tylf5l@debian>
On Mon, Jan 27, 2020 at 12:30:21PM +0000, Wei Liu wrote:
> On Mon, Jan 20, 2020 at 11:52:17AM +0000, Anthony PERARD wrote:
> > On Mon, Jan 20, 2020 at 11:50:50AM +0000, Anthony PERARD wrote:
> > > Patch series available in this git branch:
> > > https://xenbits.xen.org/git-http/people/aperard/xen-unstable.git br.python3-default-v1
> > >
> > > Hi,
> > >
> > > I think it's time for Xen to build with python3 by default.
> > >
> > > The main reason for that is that QEMU upstream don't build with python 2.x
> > > anymore, and the python binary selected by Xen build system is the one used
> > > when building qemu-xen. So now osstest failed to build QEMU upstream.
> > >
> > > Also, python2 is EOL.
> > >
> > > FYI, the hypervisor build system already select python3 by default, this change
> > > the tools side.
> >
> > I forgot to say that there's a osstest patch as well:
> > [OSSTEST PATCH] ts-xen-build-prep: Install python3-dev
>
> AIUI I don't need to wait for that patch to be applied before applying
> this series. Let me know if I'm wrong.
It just going to prevent a push :-). All build of staging will fail. So,
the osstest patch is needed before applying the patch 3/3.
Cheers,
--
Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-01-27 12:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 11:50 [Xen-devel] [XEN PATCH 0/3] Default to python3 Anthony PERARD
2020-01-20 11:50 ` [Xen-devel] [XEN PATCH 1/3] automation: Only build QEMU if Python >= 3.5 Anthony PERARD
2020-01-25 1:09 ` Doug Goldstein
2020-01-20 11:50 ` [Xen-devel] [XEN PATCH 2/3] automation: updating container to have python3-config binary Anthony PERARD
2020-01-25 1:09 ` Doug Goldstein
2020-01-20 11:50 ` [Xen-devel] [XEN PATCH 3/3] tools: Default to python3 Anthony PERARD
2020-01-27 14:41 ` Wei Liu
2020-01-20 11:52 ` [Xen-devel] [XEN PATCH 0/3] " Anthony PERARD
2020-01-27 12:30 ` Wei Liu
2020-01-27 12:36 ` Anthony PERARD [this message]
2020-01-27 14:40 ` Wei Liu
2020-01-27 14:44 ` Wei Liu
2020-02-11 11:19 ` Anthony PERARD
2020-02-11 11:25 ` Wei Liu
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=20200127123623.GL1288@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=cardoe@cardoe.com \
--cc=ian.jackson@eu.citrix.com \
--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.