From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: Eduardo Habkost <eduardo@habkost.net>,
John Snow <jsnow@redhat.com>, Beraldo Leal <bleal@redhat.com>,
Cleber Rosa <crosa@redhat.com>
Subject: [PATCH 0/2] Python: setuptools v60+ workaround
Date: Mon, 24 Jan 2022 13:56:41 -0500 [thread overview]
Message-ID: <20220124185643.641848-1-jsnow@redhat.com> (raw)
Long story short: Python 3.7/3.8 on Fedora with setuptools v60.0.0+
together create a bug that ultimately causes pylint to fail. See the
first commit message for more detail.
I sent out a hotfix last week to fix this behavior on our CI, but this
series offers a more comprehensive fix and reverts the hotfix.
John Snow (2):
Python: setuptools v60.0 workaround
Revert "python: pin setuptools below v60.0.0"
python/Makefile | 2 --
python/setup.cfg | 1 -
python/tests/iotests-pylint.sh | 3 ++-
python/tests/pylint.sh | 3 ++-
4 files changed, 4 insertions(+), 5 deletions(-)
--
2.31.1
next reply other threads:[~2022-01-24 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 18:56 John Snow [this message]
2022-01-24 18:56 ` [PATCH 1/2] Python: setuptools v60.0 workaround John Snow
2022-01-24 18:56 ` [PATCH 2/2] Revert "python: pin setuptools below v60.0.0" John Snow
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-all 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=20220124185643.641848-1-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=eduardo@habkost.net \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.