Output AppImage prefers ~/.local for pip packages

[TheLastProject]

This one confused me for a long time: Why was my Pext 0.20 AppImage stating it was Pext-0.19+18.g11a6dea?

Well, I found it when I looked at the logs:

file:///home/sylvia/.local/lib/python3.6/site-packages/pext/qml/AboutDialog.qml:87:17: QML Text: Binding loop detected for property "width"                               

After doing a "pip3 uninstall pext", it started working fine.

The output AppImages probably need some $PATH changes to prefer bundled libraries over the system ones to prevent really weird issues.

[TheAssassin]

Any suggestions which ones to set? Even if $PYTHONPATH is set, the system directories will be used as a fallback. And I'm pretty sure that miniconda internally sets sys.path to its own directories.

[TheLastProject]

I'm not sure, just the AppImage one probably should be at the start of the $PYTHONPATH. Falling back seems okay-ish, just not having things overwritten by the system by default.

[TheAssassin]

@TheLastProject that is actually the case, as mentioned above:

# create new env
$ source conda-env/bin/activate
$ python
Python 3.7.0 (default, Jun 28 2018, 13:15:42) 
[GCC 7.2.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.path
['', '.../conda-env/lib/python37.zip', '.../conda-env/lib/python3.7', '...conda-env/lib/python3.7/lib-dynload', '.../conda-env/lib/python3.7/site-packages']

[TheLastProject]

Maybe it's $PATH being the issue here then?

[TheAssassin]

How could $PATH have any influence on this?

[TheLastProject]

I honestly don't know, just guessing for some explanation of the behaviour I observed

[TheAssassin]

I can reproduce the issue. Seems like an issue within PyQt5.