unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Phil <phil@beadling.co.uk>, help-guix@gnu.org
Subject: Re: Avoiding PYTHONPATH - latest?
Date: Mon, 30 Nov 2020 14:05:58 +0100	[thread overview]
Message-ID: <86pn3vvvt5.fsf@gmail.com> (raw)
In-Reply-To: <85360rr8v5.fsf@beadling.co.uk>

Hi,

I have not re-read all the discussion about PYTHONPATH and co.

On Mon, 30 Nov 2020 at 00:22, Phil <phil@beadling.co.uk> wrote:

> But the current PYTHONPATH implementation immediately runs into problems
> when you use venvs for development, via the cannonical "pip install -e
> .".  The use of PYTHONPATH means that venvs are not created pure, they
> inherit Guix's python env which is the exact opposite to what any
> non-Guix python developer would expect.

Just to understand, is your point to be able to mix both “pip install“
and “guix install”?  If yes, it appears to me a bad idea, choose one or
the other.


> I was wondering what the current thoughts were on how Guix could
> workaround using PYTHONPATH to set base system paths?

Well, I do not remember more than the attempt of GUIX_PYTHONPATH.


All the best,
simon


  parent reply	other threads:[~2020-11-30 13:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30  0:22 Avoiding PYTHONPATH - latest? Phil
2020-11-30  9:41 ` Phil
2020-12-03 11:06   ` 宋文武
2020-11-30 13:05 ` zimoun [this message]
2020-11-30 15:04   ` Phil
2020-12-01 12:39     ` zimoun
2020-12-01 13:28       ` Phil
2020-12-01 14:54         ` zimoun
2020-12-01 18:46           ` Phil

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=86pn3vvvt5.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=phil@beadling.co.uk \
    /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.
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).