From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Jelle Licht <jlicht@fsfe.org>
Cc: 46569@debbugs.gnu.org
Subject: bug#46569: python can't find internal pip modules in environment from manifest
Date: Thu, 18 Feb 2021 13:05:47 -0500 [thread overview]
Message-ID: <87sg5tuu84.fsf@gmail.com> (raw)
In-Reply-To: <86czwz7ms3.fsf@fsfe.org> (Jelle Licht's message of "Tue, 16 Feb 2021 21:58:20 +0100")
Hi Jelle,
Jelle Licht <jlicht@fsfe.org> writes:
> Python can not load all pip-related python modules when loaded from a
> manifest file, yet seems to work fine when loaded 'directly' as part of
> a `guix environment'-invocation.
>
>
> Provided that we have a file in `hi.py':
>
> import pip
> print("halfwaypoint")
> import pip._internal.index.package_finder
> print("I made it!")
>
>
> and a `manifest.scm' with:
>
> (use-modules (gnu) (guix packages)
> (gnu packages python)
> (gnu packages python-xyz))
>
> (packages->manifest (list python python-pip))
>
>
> I can get the expected output by running:
> `guix environment --pure --ad-hoc python python-pip -- python3 hi.py' =>
>> halfwaypoint
>> I made it!
It seems that two pip versions don't cohabit very well. The same
happens if you install pip via 'pip install --user pip' (e.g., to
~/.local/bin) and try to use it.
You could try using the pip version that comes bundled with Python
itself (e.g, not installing python-pip in the same profile); if it's the
only one, it should work.
HTH,
Maxim
next prev parent reply other threads:[~2021-02-18 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 20:58 bug#46569: python can't find internal pip modules in environment from manifest Jelle Licht
2021-02-18 13:49 ` Jelle Licht
2021-02-18 16:37 ` Jelle Licht
2021-02-18 18:05 ` Maxim Cournoyer [this message]
2021-02-18 19:45 ` Jelle Licht
2021-02-18 21:18 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sg5tuu84.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=46569@debbugs.gnu.org \
--cc=jlicht@fsfe.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).