all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: PEP 668 -- Graceful cooperation between external and Python package managers
Date: Sat, 11 Sep 2021 22:36:55 -0400	[thread overview]
Message-ID: <87sfyapliw.fsf@gmail.com> (raw)
In-Reply-To: <YTeOc//PLfZI1AZJ@jasmine.lan> (Leo Famulari's message of "Tue, 7 Sep 2021 12:08:19 -0400")

Hello,

Leo Famulari <leo@famulari.name> writes:

> On Tue, Sep 07, 2021 at 04:39:28PM +0200, Maxime Devos wrote:
>> See <https://www.python.org/dev/peps/pep-0668/>.
>> I haven't looked closely into this myself.
>> It might be relevant to Guix.
>> 
>> For LWN subscribers, there is an article about the PEP:
>> <https://lwn.net/Articles/867657/>.
>
> Here is a link for everyone to read:
>
> https://lwn.net/SubscriberLink/867657/c4e77bb70e27c910/

Guix already makes life easier with dealing with Python environments
(especially with GUIX_PYTHONPATH on core-updates), but it's nice to know
this problem is getting addressed.

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.

Thanks for the link!

Maxim


  reply	other threads:[~2021-09-12  2:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07 14:39 PEP 668 -- Graceful cooperation between external and Python package managers Maxime Devos
2021-09-07 16:08 ` Leo Famulari
2021-09-12  2:36   ` Maxim Cournoyer [this message]
2021-09-12 10:34     ` Liliana Marie Prikler
2021-09-15  4:22       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sfyapliw.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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.