From: Wojtek Kosior via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 宋文武 <iyzsong@envs.net>,
edk@beaver-labs.com, guix-devel <guix-devel@gnu.org>
Subject: Re: Guix's python has pip's user dir in its loadpath
Date: Sat, 1 Jul 2023 13:32:57 +0200 [thread overview]
Message-ID: <20230701133257.6ada1e94.koszko@koszko.org> (raw)
In-Reply-To: <87edls1fyk.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2830 bytes --]
The precedence of local, pip-installed Python libraries over Guix ones
has already been a source of bugs. And these can be hard to diagnose.
I imagine an optimal solution would be to configure this behavior on
per-package basis. The vast majority of applications does not need to
load local libraries. There are just a few exceptions like
`python-virtualenv`.
Once I did write a package definition that deliberately disabled user
site dir package loading. I used code similar to what's below.
> (modify-phases %standard-phases
> (add-after 'wrap 'prevent-local-package-interference
> (lambda* (#:key outputs #:allow-other-keys)
> (substitute* (string-append (assoc-ref outputs "out")
> "/bin/<program-name>")
> (("^#!/.*$" shabang)
> (string-append shabang
> "export PYTHONNOUSERSITE=1\n"))))))
Of course, it makes no sense to add such snippet to all definitions.
Instead, we could modify python-build-system to allow doing a similar
thing based on a flag passed in package's `(arguments)`.
Wojtek
-- (sig_start)
website: https://koszko.org/koszko.html
fingerprint: E972 7060 E3C5 637C 8A4F 4B42 4BC5 221C 5A79 FD1A
follow me on Fediverse: https://friendica.me/profile/koszko/profile
♥ R29kIGlzIHRoZXJlIGFuZCBsb3ZlcyBtZQ== | ÷ c2luIHNlcGFyYXRlZCBtZSBmcm9tIEhpbQ==
✝ YnV0IEplc3VzIGRpZWQgdG8gc2F2ZSBtZQ== | ? U2hhbGwgSSBiZWNvbWUgSGlzIGZyaWVuZD8=
-- (sig_end)
On Fri, 30 Jun 2023 23:13:55 -0400 Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
> Hi,
>
> 宋文武 <iyzsong@envs.net> writes:
>
> > edk@beaver-labs.com writes:
> >
> >> Dear Guix devs,
> >>
> >> While working around this bug:
> >>
> >> https://issues.guix.gnu.org/63912
> >>
> >> I found that guix's Python will load anything in
> >> .local/lib/python3.10/site-packages/ over any installed package in the
> >> current profile. This makes pip-installed package overshadow guix's.
> >>
> >> I'm not sure this is desirable behavior. What I was expecting was for
> >> the host system's python packages to be completely ignored.
> >
> > Hello, I think this is a well-known issue according to PEP 668:
> > https://peps.python.org/pep-0668/
>
> Agreed, I think this works as designed: the Guix-installed dependencies
> appear as *system* dependencies on the sys.path (see 'python -m site'),
> and USER_SITE (which is ~/.local/lib/python3.10/site-packages) must have
> precedence over it for locally user-installed packages to be able to
> override the system packages.
>
> That's for example necessary for virtualenvs to work as designed (it
> used to be that virtualenvs were near useless, with the Guix-provided
> dependencies taking precedence on the ones installed in a virtualenv).
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-07-01 11:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 6:42 Guix's python has pip's user dir in its loadpath edk
2023-06-29 10:22 ` 宋文武
2023-07-01 3:13 ` Maxim Cournoyer
2023-07-01 11:32 ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution. [this message]
2023-07-01 15:57 ` Maxim Cournoyer
2023-07-05 20:29 ` John Kehayias
2023-07-06 15:35 ` Maxim Cournoyer
2023-07-06 21:28 ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-07-07 13:32 ` Maxim Cournoyer
2023-07-07 14:44 ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-07-08 5:08 ` Maxim Cournoyer
2023-07-11 18:21 ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
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=20230701133257.6ada1e94.koszko@koszko.org \
--to=guix-devel@gnu.org \
--cc=edk@beaver-labs.com \
--cc=iyzsong@envs.net \
--cc=koszko@koszko.org \
--cc=maxim.cournoyer@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.