[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PYTHONPATH issue analysis - part 3
From: |
Ludovic Courtès |
Subject: |
Re: PYTHONPATH issue analysis - part 3 |
Date: |
Thu, 15 Mar 2018 10:09:31 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) |
Hello,
Ricardo Wurmus <address@hidden> skribis:
> The problem might be that we are using PYTHONPATH at all. On other
> distributions this is usually not required and thus doesn’t cause any
> problems.
It’s not required because Python modules live at a fixed location, no?
How does pip deal with that? I suppose it needs to modify the search
path somehow.
> As outlined in my first email in this thread, our use of PYTHONPATH in
> wrappers seems to not have the desired effect in the presence of
> incompatible packages that are *later* in the PYTHONPATH.
>
> We also have problems when PYTHONPATH includes modules for both Python 2
> and 3, which happens automatically when these modules are installed into
> the same Guix profile. Since merely installing packages for different
> Python versions is not a problem on traditional distros (on my Fedora
> workstation I have site-packages directories for 4 different versions of
> Python) I think we should do better here.
I agree, though I must say that if PYTHONPATH is not up to the task, I’m
not sure what can be done on our side.
Thanks,
Ludo’.
- Re: PYTHONPATH issue analysis - part 3, (continued)
Re: PYTHONPATH issue analysis - part 3, Hartmut Goebel, 2018/03/13
Re: PYTHONPATH issue analysis - part 3, Ricardo Wurmus, 2018/03/14
- Re: PYTHONPATH issue analysis - part 3,
Ludovic Courtès <=
Re: PYTHONPATH issue explanation, Hartmut Goebel, 2018/03/15
Re: [PATCH] gnu: python: Honor 'GUIX_PYTHON_X_Y_SITE_PACKAGES'., 宋文武, 2018/03/17
Re: PYTHONPATH issue explanation, Hartmut Goebel, 2018/03/17