From: iyzsong@member.fsf.org (宋文武)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel@gnu.org
Subject: Re: PYTHONPATH - let's systematically tame the baest
Date: Tue, 17 Apr 2018 09:47:12 +0800 [thread overview]
Message-ID: <87po2ya9jz.fsf@member.fsf.org> (raw)
In-Reply-To: <2c8e59df-d0f7-e096-f175-a8a74e8818dc@crazy-compilers.com> (Hartmut Goebel's message of "Mon, 16 Apr 2018 16:21:00 +0200")
Hartmut Goebel <h.goebel@crazy-compilers.com> writes:
> Hi,
Hello!
>
> let's pick up on this issue and systematically design the test-cases to
> benchmark the proposed solutions. I already prepared a test-script to
> simplify this and will provide a full description as later.
>
> **Please comment if any relevant case is missing or if any case can be
> skipped**
>
> 1) Test-cases
>
> For all environments (see below) these cases must give the expected
> output - which is defined by what a "foreign distribution's" python
> would do:
> - "installed" python
> - venv with and without --system-site-packages
> - stacked venv with and without --system-site-packages
We should consider both python2 and python3, and virtual environments
created by the 'virtualenv' package.
>
> 2) Environments to be tested.
>
> The proposed solution must pass the test-suite in all of these environments:
>
> 2.1 guix environment:
>
> guix environment --ad-hoc python -- python3 testit
> --> Expected outcome: site-packages from GUIX_ENVIRONEMENT
>
> 2.2 guix environment with container:
>
> guix environment -C --ad-hoc python -- python3 testit
> --> Expected outcome: site-packages from GUIX_ENVIRONEMENT
>
> 2.3 Installed package *without setting the environment variables!*
>
> guix package -i python && ~/.guix-profile/bin/python3 testit
> --> Expected outcome: site-packages from ~/.guix-profile/
> --> Shall this work, too? Is it nice-to-have or useless?
Yeah, it's nice to have (to avoid introducing an environment variable),
but not necessary.
>
> 2.4 running from /gnu/store (directly)
>
> $(readlink -f ~/.guix-profile/bin/python3) testit
> --> Expected outcome: site-packages from /gnu/store
> --> What is the expected outcome? What is the expected
I think if we use environment variable to specify all the site-packages,
it should be the same as running from profile. It maybe different if we
resolve site-packages by the executable location...
>
> 2.5 running from /gnu/store (via link)
>
> ln -s $(readlink -f ~/.guix-profile/bin/python3)
> /tmp/test-guix-pythonA.exe ;
> /tmp/test-guix-pythonA.exe testit
> --> Expected outcome: site-packages from /gnu/store
True when we're not use the environment variable.
>
> 2.6 Installed in GuixSD
>
> --> Do we need to test this? Or is this already covered by one of
> the other cases?
For this, there is nothing special about GuixSD.
Had you review my 'GUIX_PYTHON_X_Y_SITE_PACKAGES' patch? I think it's
enough to support both python2 and python3 in the same profile:
http://lists.gnu.org/archive/html/guix-devel/2018-03/msg00238.html
Thanks!
next prev parent reply other threads:[~2018-04-17 1:47 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 10:53 PYTHONPATH woes Ricardo Wurmus
2018-02-20 15:01 ` Pjotr Prins
2018-02-20 15:18 ` Andy Wingo
2018-02-20 16:40 ` Pjotr Prins
2018-02-20 15:30 ` Ricardo Wurmus
2018-02-21 21:58 ` Hartmut Goebel
2018-02-22 15:30 ` Ricardo Wurmus
2018-02-22 18:35 ` Hartmut Goebel
2018-02-22 20:42 ` Hartmut Goebel
2018-02-23 8:45 ` Vincent Legoll
2018-02-23 12:36 ` Hartmut Goebel
2018-02-23 16:59 ` Pjotr Prins
2018-02-23 19:36 ` Ricardo Wurmus
2018-02-23 23:54 ` Pjotr Prins
2018-02-24 10:44 ` Hartmut Goebel
2018-02-24 10:49 ` Hartmut Goebel
2018-02-27 11:43 ` PYTHONPATH issue analysis - part 1 (was: PYTHONPATH woes) Hartmut Goebel
2018-03-13 21:54 ` PYTHONPATH issue analysis - part 1 Hartmut Goebel
2018-02-27 11:49 ` PYTHONPATH issue analysis - part 2 (was: PYTHONPATH woes) Hartmut Goebel
2018-03-11 21:47 ` PYTHONPATH issue analysis - part 3 " Hartmut Goebel
2018-03-13 21:23 ` PYTHONPATH issue analysis - part 3 Ludovic Courtès
2018-03-13 21:44 ` Pjotr Prins
2018-03-13 22:02 ` Hartmut Goebel
2018-03-14 7:49 ` Pjotr Prins
2018-03-14 9:04 ` Hartmut Goebel
2018-03-14 18:21 ` Pjotr Prins
2018-03-15 19:48 ` Hartmut Goebel
2018-03-13 21:47 ` Hartmut Goebel
2018-03-14 9:41 ` Ludovic Courtès
2018-03-13 21:51 ` Hartmut Goebel
2018-03-14 0:10 ` Ricardo Wurmus
2018-03-15 9:09 ` Ludovic Courtès
2018-03-15 19:30 ` PYTHONPATH issue explanation Hartmut Goebel
2018-03-17 1:41 ` 宋文武
2018-03-17 10:07 ` Ricardo Wurmus
2018-03-17 22:46 ` Hartmut Goebel
2018-03-17 22:53 ` Hartmut Goebel
2018-03-17 11:18 ` [PATCH] gnu: python: Honor 'GUIX_PYTHON_X_Y_SITE_PACKAGES' 宋文武
2018-03-17 21:53 ` Hartmut Goebel
2018-03-18 0:04 ` 宋文武
2018-03-18 0:07 ` 宋文武
2018-03-17 22:04 ` PYTHONPATH issue explanation Hartmut Goebel
2018-03-18 0:57 ` 宋文武
2018-03-18 10:05 ` 宋文武
2018-03-24 20:47 ` Chris Marusich
2018-04-16 14:21 ` PYTHONPATH - let's systematically tame the baest Hartmut Goebel
2018-04-17 1:47 ` 宋文武 [this message]
2018-04-17 7:03 ` Hartmut Goebel
2018-04-18 8:34 ` Ricardo Wurmus
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=87po2ya9jz.fsf@member.fsf.org \
--to=iyzsong@member.fsf.org \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.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.