TheAssassin

@TheLastProject that is actually the case, as mentioned above: ```bash # 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,...

How could `$PATH` have any influence on this?

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

What's the intention behind this "issue"?

Note for \: the SSL part in the AppRun script isn't strictly necessary, fixed some issues with [Pext](https://github.com/Pext/Pext)'s plugin system IIRC. See https://github.com/Pext/Pext/blob/e0cf8cfd68827a678317a75226aacb8e23fe1a16/travis/build-appimage.sh#L29 for more information.

Doesn't seem safe at all. And requires running an AppImage, which isn't possible during a plugin run. I think that's something to put in the docs as "potential optimization", but...

Duplicate of/related to https://github.com/linuxdeploy/linuxdeploy-plugin-conda/issues/12. This can't be done simply, since we cannot guess the path of the Python installation in the AppDir, the paths in shebangs are either absolute or...

As stated in #12, Python scripts should never call each other "directly", as that's anything but portable. And for running at first, `python -m "name_of_module"` is usually good enough. If...

Yes, it's needed with this. But the solution is not really to export any variables. That only works when the shebang uses `/usr/bin/env` or doesn't specify an absolute path altogether....

Duplicate of #10.