From: "Yuwei Chen" <yuwei.chen@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"crobinso@redhat.com" <crobinso@redhat.com>,
Liming Gao <gaoliming@byosoft.com.cn>
Cc: "Feng, Bob C" <bob.c.feng@intel.com>,
"Liu, Zhiguang" <zhiguang.liu@intel.com>
Subject: Re: [edk2-devel] [PATCH 0/3] BaseTools: fix some python DeprecationWarnings
Date: Tue, 10 Aug 2021 07:48:17 +0000 [thread overview]
Message-ID: <DM5PR11MB1594F9F4E692A2BBDCE21DE096F79@DM5PR11MB1594.namprd11.prod.outlook.com> (raw)
In-Reply-To: <cover.1627070203.git.crobinso@redhat.com>
Hi Robinson,
When we doing the internal test, the issue is found that py27 is blocked by this patch.
You can reproduce the error with below steps:
For Linux:
[Error Reproduce steps]
$ export PYTHON3_ENABLE=FALSE
$ export PYTHON_COMMAND=/usr/bin/python2.7
$ build -p OvmfPkg/OvmfPkgIa32X64.dsc -a IA32 -a X64 -t GCC5
Active Platform = /home/jshi19/wksp_efi/edk2-3/OvmfPkg/OvmfPkgIa32X64.dsc
......
- Failed -
Build end time: 13:00:59, Aug.10 2021
Build total time: 00:00:07
[After Reverting the patch]
$ git revert 0b1b0a9674e27c858f05436ed92250f4498245cf
$ build -p OvmfPkg/OvmfPkgIa32X64.dsc -a IA32 -a X64 -t GCC5
Pass
For Windows:
[Error Reproduce steps]
set PYTHON3_ENABLE=FALSE
set PYTHON_COMMAND=C:\Python27\python.exe
build -p OvmfPkg\OvmfPkgIa32X64.dsc -a IA32 -a X64 -t VS2015x86
Active Platform = c:\users\yuweiche\code\edk2\edk2\OvmfPkg\OvmfPkgIa32X64.dsc
......
- Failed -
Build end time: 15:40:35, Aug.10 2021
Build total time: 00:00:07
[After Reverting the patch]
$ git revert 0b1b0a9674e27c858f05436ed92250f4498245cf
$ build -p OvmfPkg\OvmfPkgIa32X64.dsc -a IA32 -a X64 -t VS2015x86
- Done -
Build end time: 15:35:16, Aug.10 2021
Build total time: 00:01:58
Hope you can fix this bug. 😊 @crobinso@redhat.com
Hi Liming @Liming Gao, what do you think about this issue? If we need fix it before this quarter release?
Thanks,
Yuwei (Christine)
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Cole
> Sent: Saturday, July 24, 2021 4:02 AM
> To: devel@edk2.groups.io
> Cc: Cole Robinson <crobinso@redhat.com>
> Subject: [edk2-devel] [PATCH 0/3] BaseTools: fix some python
> DeprecationWarnings
>
> This addresses some python DeprecationWarnings that are popping up with
> python 3.10
>
> Cole Robinson (3):
> build: Fix python3.10 threading DeprecationWarnings
> python: Replace distutils.utils.split_quotes with shlex.split
> BaseTools: Drop check for distutils.utils
>
> .../Source/Python/AutoGen/UniClassObject.py | 4 +-
> .../Python/UPT/Library/UniClassObject.py | 4 +-
> BaseTools/Source/Python/build/build.py | 48 +++++++++----------
> BaseTools/Tests/RunTests.py | 7 ---
> 4 files changed, 28 insertions(+), 35 deletions(-)
>
> --
> 2.31.1
>
>
>
>
>
prev parent reply other threads:[~2021-08-10 7:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 20:02 [PATCH 0/3] BaseTools: fix some python DeprecationWarnings Cole
2021-07-23 20:02 ` [PATCH 1/3] build: Fix python3.10 threading DeprecationWarnings Cole
2021-07-23 20:02 ` [PATCH 2/3] python: Replace distutils.utils.split_quotes with shlex.split Cole
2021-07-23 20:02 ` [PATCH 3/3] BaseTools: Drop check for distutils.utils Cole
2021-07-26 6:20 ` [edk2-devel] " Yuwei Chen
2021-07-26 3:52 ` [edk2-devel] [PATCH 0/3] BaseTools: fix some python DeprecationWarnings Bob Feng
2021-08-10 7:48 ` Yuwei Chen [this message]
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=DM5PR11MB1594F9F4E692A2BBDCE21DE096F79@DM5PR11MB1594.namprd11.prod.outlook.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