From: Paolo Bonzini <pbonzini@redhat.com>
To: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Beraldo Leal" <bleal@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>
Subject: Re: [RFC PATCH 1/3] python: add mkvenv.py
Date: Wed, 29 Mar 2023 14:56:00 +0200 [thread overview]
Message-ID: <d49d0152-ff58-a317-7eca-a243ed080ca0@redhat.com> (raw)
In-Reply-To: <20230328211119.2748442-2-jsnow@redhat.com>
On 3/28/23 23:11, John Snow wrote:
> + # venv class is cute and toggles this off before post_setup,
> + # but we need it to decide if we want to generate shims or not.
Ha, yeah that's a bug in the venv package. post_setup() can already run
with system_site_packages reverted to True.
> + for entry_point in entry_points:
> + # Python 3.8 doesn't have 'module' or 'attr' attributes
> + if not (hasattr(entry_point, 'module') and
> + hasattr(entry_point, 'attr')):
> + match = pattern.match(entry_point.value)
> + assert match is not None
> + module = match.group('module')
> + attr = match.group('attr')
> + else:
> + module = entry_point.module
> + attr = entry_point.attr
> + yield {
> + 'name': entry_point.name,
> + 'module': module,
> + 'import_name': attr,
> + 'func': attr,
What about using a dataclass or namedtuple instead of a dictionary?
>
> +
> + try:
> + entry_points = _get_entry_points()
> + except ImportError as exc:
> + logger.debug("%s", str(exc))
> + raise Ouch(
> + "Neither importlib.metadata nor pkg_resources found, "
> + "can't generate console script shims.\n"
> + "Use Python 3.8+, or install importlib-metadata, or setuptools."
> + ) from exc
Why not put this extra try/except inside _get_entry_points()?
> +
> + # Test for ensurepip:
> + try:
> + import ensurepip
Use find_spec()?
BTW, another way to repair Debian 10's pip is to create a symbolic link
to sys.base_prefix + '/share/python-wheels' in sys.prefix +
'/share/python-wheels'. Since this is much faster, perhaps it can be
done unconditionally and checkpip mode can go away together with
self._context?
Paolo
next prev parent reply other threads:[~2023-03-29 12:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 21:11 [RFC PATCH 0/3] configure: create a python venv and install meson John Snow
2023-03-28 21:11 ` [RFC PATCH 1/3] python: add mkvenv.py John Snow
2023-03-29 12:56 ` Paolo Bonzini [this message]
2023-03-30 14:00 ` John Snow
2023-03-31 8:44 ` Paolo Bonzini
2023-03-31 10:01 ` Paolo Bonzini
2023-04-13 16:10 ` John Snow
2023-04-13 16:26 ` John Snow
2023-03-28 21:11 ` [RFC PATCH 2/3] tests: add python3-venv dependency John Snow
2023-03-28 21:11 ` [RFC PATCH 3/3] configure: install meson to a python virtual environment John Snow
2023-03-29 12:32 ` Paolo Bonzini
2023-03-29 12:53 ` Daniel P. Berrangé
2023-03-29 13:27 ` Paolo Bonzini
2023-03-29 13:31 ` Daniel P. Berrangé
2023-04-12 1:27 ` John Snow
2023-03-29 13:02 ` [RFC PATCH 0/3] configure: create a python venv and install meson Paolo Bonzini
2023-03-30 14:11 ` John Snow
2023-03-31 8:40 ` Paolo Bonzini
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=d49d0152-ff58-a317-7eca-a243ed080ca0@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=philmd@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).