From: 宋文武 <iyzsong@outlook.com>
To: Phil <phil@beadling.co.uk>
Cc: help-guix@gnu.org
Subject: Re: Avoiding PYTHONPATH - latest?
Date: Thu, 03 Dec 2020 19:06:57 +0800 [thread overview]
Message-ID: <TYAP286MB0185AEDC7896E698AF4FBDE6A3F20@TYAP286MB0185.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <851rgbqizp.fsf@beadling.co.uk> (phil@beadling.co.uk's message of "Mon, 30 Nov 2020 09:41:46 +0000")
Hello!
Phil <phil@beadling.co.uk> writes:
>> I've been having an argument with myself over the last 4 days about if
>> Guix's use of PYTHONPATH is a necessary evil or avoidable on a foreign OS.
>>
>> I've found references to a similar discussion last year, and reference
>> to using a 'fake virtual environment' (does anyone have a reference to
>> the other thread referenced where fake venvs are demonstrated as not
>> working):
I remembered did that too, I think it works in most cases.
<https://lists.gnu.org/archive/html/guix-devel/2018-03/msg00223.html>
>>
>> https://lists.gnu.org/archive/html/guix-devel/2019-06/msg00204.html
>> https://lists.gnu.org/archive/html/guix-devel/2019-06/msg00221.html
>>
>> I had what I think is a similar idea over the weekend and tried it out.
>>
>> Reading the mechanics of venvs as per PEP:
>> https://www.python.org/dev/peps/pep-0405
>>
>> I decided to see if I added a fake pyvenv.cfg to the python.scm package
>> could allow for us to drop the use of PYTHONPATH completely.
I had came up with adding another environment variable
‘GUIX_PYTHON_X_Y_SITE_PACKAGES’:
<https://lists.gnu.org/archive/html/guix-devel/2018-03/msg00226.html>
But didn’t made it in, feel free take it if useful, thanks!
next prev parent reply other threads:[~2020-12-03 11:27 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 ` 宋文武 [this message]
2020-11-30 13:05 ` zimoun
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=TYAP286MB0185AEDC7896E698AF4FBDE6A3F20@TYAP286MB0185.JPNP286.PROD.OUTLOOK.COM \
--to=iyzsong@outlook.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).