From: "Zhu, Yonghong" <yonghong.zhu@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
"heyi.guo@linaro.org" <heyi.guo@linaro.org>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Gary Ching-Pang Lin <glin@suse.com>,
"Gao, Liming" <liming.gao@intel.com>,
"Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: Can we use python 3 to build edk2?
Date: Mon, 27 Aug 2018 13:31:34 +0000 [thread overview]
Message-ID: <B9726D6DCCFB8B4CA276A9169B02216D520EE2B5@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <d58f2dd9-9f48-ac4a-80d7-cb859c6c086a@redhat.com>
We have a bugzilla. https://bugzilla.tianocore.org/show_bug.cgi?id=55
Current I am working on it. And planned to finish to migrate to Python 3 before end of October.
Best Regards,
Zhu Yonghong
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Laszlo Ersek
Sent: Monday, August 27, 2018 9:27 PM
To: heyi.guo@linaro.org
Cc: Kinney, Michael D <michael.d.kinney@intel.com>; edk2-devel@lists.01.org; Gary Ching-Pang Lin <glin@suse.com>; Gao, Liming <liming.gao@intel.com>
Subject: Re: [edk2] Can we use python 3 to build edk2?
On 08/27/18 13:53, heyi.guo@linaro.org wrote:
> It is said that python3 is not compatible with python2.
Did you mean s/said/sad/? :)
> Can we use python3 to build edk2?
Gary and Mike wrote several BaseTools patches for python3 compatibility; I'm unsure if we have a high-level tracker BZ for that. I don't know the current status. Adding Mike and Gary.
Thanks
Laszlo
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-08-27 13:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 11:53 Can we use python 3 to build edk2? heyi.guo
2018-08-27 13:22 ` Zhu, Yonghong
2018-08-27 13:26 ` Laszlo Ersek
2018-08-27 13:31 ` Zhu, Yonghong [this message]
2018-08-27 15:58 ` Laszlo Ersek
2018-08-28 1:00 ` heyi.guo
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-list 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=B9726D6DCCFB8B4CA276A9169B02216D520EE2B5@SHSMSX103.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/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