From: Laszlo Ersek <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
"afish@apple.com" <afish@apple.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [RFC] Edk2 BaseTools Python3 Migration Update
Date: Wed, 26 Dec 2018 22:16:29 +0100 [thread overview]
Message-ID: <13e879af-4b9f-50d4-c945-6b94a88ef829@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E39130F@SHSMSX104.ccr.corp.intel.com>
On 12/25/18 08:50, Gao, Liming wrote:
> Hi, all
> On Python3 migration
> https://bugzilla.tianocore.org/show_bug.cgi?id=55, we update Edk2
> BaseTools python source code with the compatible syntax to support
> Python2 and Python3 both. Here is code
> https://github.com/lgao4/edk2/tree/Python3 for dry run. To enable
> Python3, you just need to set PYTHON3_ENABLE environment as TRUE, then
> type edksetup.bat/edksetup.sh.
Hopefully I can test this sometime after I return from my PTO. No
promises as to when, for now.
> Without this setting, BaseTools still run with Python2. So, there is
> no change for current usage model with Python27.
>
> But, we have no enough resource to fully verify Python2 and Python3
> both. We will focus on Python3 validation. If anyone can help verify
> Python2, it will be great. And, if you meet with the issue on Python2,
> please file BZ. We still fix them.
Sounds good to me. I expect that I'll keep building upstream OVMF and
ArmVirtQemu on my RHEL7 laptop for a good while, using Python 2.
Thanks!
Laszlo
next prev parent reply other threads:[~2018-12-26 21:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-25 7:50 [RFC] Edk2 BaseTools Python3 Migration Update Gao, Liming
2018-12-26 21:16 ` Laszlo Ersek [this message]
[not found] ` <20181228103951.GN4206@GaryWorkstation>
2018-12-29 6:07 ` Gao, Liming
2018-12-31 0:15 ` Laszlo Ersek
2019-01-02 1:52 ` Gao, Liming
2019-01-04 3:29 ` Gao, Liming
2019-01-07 19:04 ` Laszlo Ersek
2019-01-08 16:25 ` Laszlo Ersek
2019-01-02 9:26 ` Gary Lin
2019-01-07 8:39 ` Ni, Ruiyu
2019-01-07 13:41 ` Gao, Liming
2019-01-07 19:04 ` Laszlo Ersek
2019-01-08 14:22 ` Gao, Liming
2019-01-08 16:22 ` Carsey, Jaben
2019-01-08 17:25 ` Laszlo Ersek
2019-01-08 18:05 ` Carsey, Jaben
2019-01-09 0:43 ` Gao, Liming
2019-01-09 18:41 ` Carsey, Jaben
2019-01-09 10:13 ` Laszlo Ersek
2019-01-08 17:22 ` Laszlo Ersek
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=13e879af-4b9f-50d4-c945-6b94a88ef829@redhat.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