Re: PYTHONPATH issue explanation

2018-03-17 Thread Hartmut Goebel
Am 17.03.2018 um 11:07 schrieb Ricardo Wurmus: > What I don’t like about this solution is that PYTHONHOME can only hold a > single directory, so composing profiles (that use the same Python > variant) would no longer work. I prefer the What exactly do you mean with "composing profiles"? This

Re: PYTHONPATH issue explanation

2018-03-17 Thread Hartmut Goebel
Hi, I agree with Ricardo: We first should agree on what we want to implement. I created a pad at [1] for collecting all test-cases and the expected results. Please add you test-cases there. Thanks! [1] https://semestriel.framapad.org/p/guix-python-site-packages-test-cases Am 17.03.2018 um

Re: python-build-system: Delete .egg-info file created in phase check.

2018-03-17 Thread Mark H Weaver
Hi Hartmut, I just now came across the code you wrote back in Oct 2016 to delete .egg-info files created during the 'check' phase in python-build-system: > From b002f964bb3d69c77856ea7dcadfe82383050512 Mon Sep 17 00:00:00 2001 > From: Hartmut Goebel > Date: Fri, 7

Re: PYTHONPATH issue explanation

2018-03-17 Thread Hartmut Goebel
Am 17.03.2018 um 11:07 schrieb Ricardo Wurmus: > >> - sys.prefix and sys.exec_prefix would still point to the store, not to >> the profile. This might break Python appications expecting >> site-packages to be below sys.prefix. > Is this an actual problem? Do you know of applications that

Re: [PATCH] gnu: python: Honor 'GUIX_PYTHON_X_Y_SITE_PACKAGES'.

2018-03-17 Thread 宋文武
iyzs...@member.fsf.org (宋文武) writes: >> I plan to implement option 1 by adding a "sitecustomize.py" (better >> than modify "site.py") into the python packages, and modify >> "search-path-specification" to use "GUIX_PYTHON_X_Y_SITE_PACKAGES". > > Patch coming: > > [patch with typo...] > > > This

Re: PYTHONPATH issue explanation

2018-03-17 Thread 宋文武
Hartmut Goebel writes: > Hi, > > I agree with Ricardo: We first should agree on what we want to > implement. Okay. > > I created a pad at [1] for collecting all test-cases and the expected > results. Please add you test-cases there. Thanks! > > [1]

Re: [PATCH] gnu: python: Honor 'GUIX_PYTHON_X_Y_SITE_PACKAGES'.

2018-03-17 Thread 宋文武
Hartmut Goebel writes: > Am 17.03.2018 um 12:18 schrieb 宋文武: > > I plan to implement option 1 by adding a "sitecustomize.py" (better > than modify "site.py") into the python packages, and modify > "search-path-specification" to use "GUIX_PYTHON_X_Y_SITE_PACKAGES".

Re: Posts in languages other than English on help-guix?

2018-03-17 Thread Chris Marusich
Chris Marusich writes: > l...@gnu.org (Ludovic Courtès) writes: > >> Hello Guix! >> >> What about allowing posts on help-guix in one of the languages that >> regular contributors know, in addition to English? > > I like it! Here's a patch for Japanese. Is there anything

Re: [PATCH] gnu: python: Honor 'GUIX_PYTHON_X_Y_SITE_PACKAGES'.

2018-03-17 Thread Hartmut Goebel
Am 17.03.2018 um 12:18 schrieb 宋文武: >> I plan to implement option 1 by adding a "sitecustomize.py" (better >> than modify "site.py") into the python packages, and modify >> "search-path-specification" to use "GUIX_PYTHON_X_Y_SITE_PACKAGES". Sorry, do say, but does not work in a virtual

Re: Posts in languages other than English on help-guix?

2018-03-17 Thread Chris Marusich
l...@gnu.org (Ludovic Courtès) writes: > Hello Guix! > > What about allowing posts on help-guix in one of the languages that > regular contributors know, in addition to English? I like it! Here's a patch for Japanese. Is there anything else I need to add, or is that it? I didn't test this

[PATCH] gnu: python: Honor 'GUIX_PYTHON_X_Y_SITE_PACKAGES'.

2018-03-17 Thread 宋文武
> I plan to implement option 1 by adding a "sitecustomize.py" (better > than modify "site.py") into the python packages, and modify > "search-path-specification" to use "GUIX_PYTHON_X_Y_SITE_PACKAGES". Patch coming: >From d9c273c0ee8c5e87b12b37a325c649f8df808af3 Mon Sep 17 00:00:00 2001 From:

Re: PYTHONPATH issue explanation

2018-03-17 Thread Ricardo Wurmus
宋文武 writes: > Option 2, "GUIX_PYTHONHOME_X_Y" can not be used in the build-system > unless we make a union of python inputs For texlive we create a temporary union in the build system, so this shouldn’t be an unsurmountable obstacle. What I don’t like about this