public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>,
	"Ni, Ray" <ray.ni@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"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: Mon, 7 Jan 2019 20:04:04 +0100	[thread overview]
Message-ID: <5e943b6c-6df2-fe06-198e-5ff5ab43c9a0@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E3AD26C@SHSMSX152.ccr.corp.intel.com>

On 01/07/19 14:41, Gao, Liming wrote:
> Ray:
>  I think this proposal is good to recommend Python3 as the default interpreter. I summary the updated proposal. 
> 
> 1. PYTHON3_ENABLE env is not set. edksetup.bat/edksetup.sh will find higher version python installed in OS. If Python3 is found, Python3 will be used. Then, if python2 is found, and python2 is used. If not found, report error and stop build. This will change the default python interpreter from Python2 to Python3 when they both are installed. 
> 2. PYTHON3_EANBLE env is set to TRUE. edksetup.bat/edksetup.sh will find Python3. If Python3 is found, Python3 will be used. If not found, report error and stop build.
> 3. PYTHON3_ENABLE env is set to not TRUE. edksetup.bat/edksetup.sh will find Python2. If Python2 is found, Python2 will be used. If not found, report error and stop build.
> Once Python is found, edksetup.bat/edksetup.sh and build tool will both print message to let user aware which version python tool is used in this build. 

If we're going for this level of flexibility, I'd like to suggest /
request another improvement. Some Linux distros intend to accommodate
multiple Python3 versions at the same time (this is not a typo; I don't
mean Python2+Python3, but multiple Python3 versions). So basically I'd
suggest that we offer a method for specifying a python version
(2/3/auto-detect), plus, in case a specific major version is specified,
that we allow the user to specify the precise interpreter pathname too.

Thanks,
Laszlo


  reply	other threads:[~2019-01-07 19:04 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
     [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 [this message]
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=5e943b6c-6df2-fe06-198e-5ff5ab43c9a0@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