[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PYTHONPATH woes
|
From: |
Pjotr Prins |
|
Subject: |
Re: PYTHONPATH woes |
|
Date: |
Tue, 20 Feb 2018 17:40:02 +0100 |
|
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Tue, Feb 20, 2018 at 04:18:40PM +0100, Andy Wingo wrote:
> In Guix we don't set LD_LIBRARY_PATH but we do set PYTHONPATH, so it's
> not quite the same I don't think.
Not exactly the same, but close enough ;). But it is clearer now that
mixing is the problem. Ricardos .pth may be an option if that works,
or we introduce a separate GUIX_PYTHONPATH2 and GUIX_PYTHONPATH for 3.
Python2 is at end of life, so we may set an example there for others.
Even so, I don't think it will solve the particular conflict that
Ricardo was describing. There will always be hairy mix-ins.
Pj.
--
- PYTHONPATH woes, Ricardo Wurmus, 2018/02/20
- Re: PYTHONPATH woes, Pjotr Prins, 2018/02/20
- Re: PYTHONPATH woes, Hartmut Goebel, 2018/02/21
- Re: PYTHONPATH woes, Ricardo Wurmus, 2018/02/22
- Re: PYTHONPATH woes, Hartmut Goebel, 2018/02/23
- Re: PYTHONPATH woes, Pjotr Prins, 2018/02/23
- Re: PYTHONPATH woes, Ricardo Wurmus, 2018/02/23
- Re: PYTHONPATH woes, Pjotr Prins, 2018/02/23