From: "Bob Feng" <bob.c.feng@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"crobinso@redhat.com" <crobinso@redhat.com>
Subject: Re: [edk2-devel] [PATCH 0/3] BaseTools: fix some python DeprecationWarnings
Date: Mon, 26 Jul 2021 03:52:28 +0000 [thread overview]
Message-ID: <DM6PR11MB407323D4B9CEF8BF80FE27E9C9E89@DM6PR11MB4073.namprd11.prod.outlook.com> (raw)
In-Reply-To: <cover.1627070203.git.crobinso@redhat.com>
This patch set is good to me.
Reviewed-by: Bob Feng <bob.c.feng@intel.com>
-----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
next prev parent reply other threads:[~2021-07-26 3:52 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 ` Bob Feng [this message]
2021-08-10 7:48 ` [edk2-devel] [PATCH 0/3] BaseTools: fix some python DeprecationWarnings Yuwei Chen
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=DM6PR11MB407323D4B9CEF8BF80FE27E9C9E89@DM6PR11MB4073.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