all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: zimoun <zimon.toutoune@gmail.com>,
	 Guix Devel <guix-devel@gnu.org>,
	Mathieu Othacehe <othacehe@gnu.org>
Subject: Re: Release progress, week 8
Date: Mon, 05 Dec 2022 15:43:36 +0100	[thread overview]
Message-ID: <87pmcxrjvr.fsf@gnu.org> (raw)
In-Reply-To: <877cz77mzo.fsf@gmail.com> (Maxim Cournoyer's message of "Sun, 04 Dec 2022 00:32:11 -0500")

Hi,

Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:

> Thank you for writing it!  It looks good, though I think the explanation
> of the benefit of GUIX_PYTHONPATH is a bit backward; one of the main
> goals was to avoid having foreign distributions break spectacularly
> because of Guix exposing their (sometimes incompatible) Python libraries
> via the shared PYTHONPATH.  It also fixed a sometimes useful use case of
> using Python's virtualenv on top of Guix.

Oh I see.  Could you amend this part, or propose something I can squeeze
in?  As you can see, I’m no expert on these matters.  :-)

Thanks for your feedback!

Ludo’.


  parent reply	other threads:[~2022-12-05 14:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 22:45 Release progress, week 8 Ludovic Courtès
2022-12-02 23:48 ` Vagrant Cascadian
2022-12-03 17:53   ` Ludovic Courtès
2022-12-04  1:55     ` missing sanity check Vagrant Cascadian
2022-12-03 10:10 ` Release progress, week 8 zimoun
2022-12-04  5:32   ` Maxim Cournoyer
2022-12-04 10:38     ` zimoun
2022-12-05 14:43     ` Ludovic Courtès [this message]
2022-12-03 17:55 ` Julien Lepiller
2022-12-05 14:44   ` Ludovic Courtès
2022-12-04 12:06 ` Mathieu Othacehe
2022-12-06 14:32   ` Ludovic Courtès
2022-12-07  9:34     ` Mathieu Othacehe
2022-12-06 16:51   ` Ludovic Courtès

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=87pmcxrjvr.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=othacehe@gnu.org \
    --cc=zimon.toutoune@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.