[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PEP 668 -- Graceful cooperation between external and Python package

From: Maxim Cournoyer
Subject: Re: PEP 668 -- Graceful cooperation between external and Python package managers
Date: Wed, 15 Sep 2021 00:22:04 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)


Liliana Marie Prikler <> writes:

> Hi,
> Am Samstag, den 11.09.2021, 22:36 -0400 schrieb Maxim Cournoyer:
>> IIUC, PEP 668 is about *warning* a pip user when installing a package
>> would shadow a system one; it does so by reading a EXTERNALLY-MANAGED
>> file in the Python library site-packages directory.
>> So simply put, all we have to do to enable this future warning in pip
>> is to install an EXTERNALLY-MANAGED file as a phase in our
>> python-build-system.
> Imho I don't think Guix needs to do anything to address PEP 668.  PEP
> 668 concerns traditional distros, in which pip and the distro package
> manager may both write to the same location (that location typically
> being /usr/lib).  IIUC it does not concern Nix or Guix, whose store
> paths should already not be written to by pip.

pip defaults to install to a user location nowadays (pip install
--user) when run as an unprivileged user [0], so even on traditional
distributions, the temptation to "sudo pip install" things and overwrite
the distro's files has been reduced.

IIUC, the EXTERNALLY-MANAGED file would also warn users when they
override (as in shadow) an already available library installed at the
system level, which could be used on Guix also (although the benefit
seems small to me).



reply via email to

[Prev in Thread] Current Thread [Next in Thread]