From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Hanna Reitz" <hreitz@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
qemu-block@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>,
"Daniel Berrange" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Michael Roth" <michael.roth@amd.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>, "John Snow" <jsnow@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: [PATCH 4/7] configure: Add nice hint to Python failure message
Date: Thu, 9 Feb 2023 10:40:31 -0500 [thread overview]
Message-ID: <20230209154034.983044-5-jsnow@redhat.com> (raw)
In-Reply-To: <20230209154034.983044-1-jsnow@redhat.com>
If we begin requiring Python 3.7+, a few platforms are going to need to
install an additional package.
This is at least mildly annoying to the user (and I hate negative
attention), so solve the user's problem for them before they get a
chance to become irritated while searching on Google for how to install
newer Python packages.
Signed-off-by: John Snow <jsnow@redhat.com>
---
configure | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/configure b/configure
index ea8c973d13b..bf512273f44 100755
--- a/configure
+++ b/configure
@@ -1058,7 +1058,10 @@ fi
if ! check_py_version "$python"; then
error_exit "Cannot use '$python', Python >= 3.6 is required." \
- "Use --python=/path/to/python to specify a supported Python."
+ "Use --python=/path/to/python to specify a supported Python." \
+ "Maybe try:" \
+ " openSUSE Leap 15.3+: zypper install python39" \
+ " CentOS 8: dnf install python38"
fi
# Suppress writing compiled files
--
2.39.0
next prev parent reply other threads:[~2023-02-09 15:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 15:40 [PATCH 0/7] Python: Drop support for Python 3.6 John Snow
2023-02-09 15:40 ` [PATCH 1/7] python: support pylint 2.16 John Snow
2023-02-09 16:01 ` Philippe Mathieu-Daudé
2023-02-09 17:49 ` Beraldo Leal
2023-02-09 15:40 ` [PATCH 2/7] Python: drop pipenv John Snow
2023-02-09 15:40 ` [PATCH 3/7] configure: Look for auxiliary Python installations John Snow
2023-02-10 19:45 ` Eric Blake
2023-02-15 20:10 ` John Snow
2023-02-09 15:40 ` John Snow [this message]
2023-02-09 15:40 ` [PATCH 5/7] testing: Add Python >= 3.7 to Centos, OpenSuSE John Snow
2023-02-09 15:56 ` Thomas Huth
2023-02-09 16:10 ` John Snow
2023-02-10 10:38 ` Daniel P. Berrangé
2023-02-15 20:25 ` John Snow
2023-02-09 15:40 ` [PATCH 6/7] CI: Stop building docs on centos8 John Snow
2023-02-09 15:57 ` Thomas Huth
2023-02-09 16:05 ` Philippe Mathieu-Daudé
2023-02-09 22:43 ` Paolo Bonzini
2023-02-09 23:32 ` John Snow
2023-02-10 10:30 ` Paolo Bonzini
2023-02-15 20:31 ` John Snow
2023-02-09 15:40 ` [PATCH 7/7] Python: Drop support for Python 3.6 John Snow
2023-02-09 16:27 ` Daniel P. Berrangé
2023-02-09 16:40 ` John Snow
2023-02-09 18:03 ` Daniel P. Berrangé
2023-02-09 21:15 ` 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=20230209154034.983044-5-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/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.