Ludovic Courtès <l...@gnu.org> writes: > I may well have missed something (sorry about that!), but what are “the > problems related to how Guix is using PYTHONPATH”? > > My first reaction is that Guix is not doing anything special with > PYTHONPATH, and only defining it as documented by upstream.
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. 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. -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net
