-
Notifications
You must be signed in to change notification settings - Fork 13
Runs the system-installed Python #25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Duplicate of/related to #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 it's about things in |
As stated in #12, Python scripts should never call each other "directly", as that's anything but portable. And for running at first, If either of the solutions above works (I'd favor the |
I think we need some sort of |
Yes, it's needed with this. But the solution is not really to export any variables. That only works when the shebang uses |
This removes some of the wrong paths pointing to the build location of the AppImage by using a different shebang and some environment variables. Fixes linuxdeploy#12, linuxdeploy#25 and linuxdeploy#32
This removes some of the wrong paths pointing to the build location of the AppImage by using a different shebang and some environment variables. Fixes linuxdeploy#12, linuxdeploy#25 and linuxdeploy#32
This removes some of the wrong paths pointing to the build location of the AppImage by using a different shebang and some environment variables. Fixes linuxdeploy#12, linuxdeploy#25 and linuxdeploy#32
This removes some of the wrong paths pointing to the build location of the AppImage by using a different shebang and some environment variables. Fixes linuxdeploy#12, linuxdeploy#25 and linuxdeploy#32
This removes some of the wrong paths pointing to the build location of the AppImage by using a different shebang and some environment variables. Fixes linuxdeploy#12, linuxdeploy#25 and linuxdeploy#32
This removes some of the wrong paths pointing to the build location of the AppImage by using a different shebang and some environment variables. Fixes linuxdeploy#12, linuxdeploy#25 and linuxdeploy#32
This removes some of the wrong, absolute paths pointing to the build location of the AppImage by using a different shebang and some environment variables, set by the linuxdeploy-plugin-conda-hook at the AppImage start. Fixes linuxdeploy#12, fixes linuxdeploy#25 and fixes linuxdeploy#32
This removes some of the wrong, absolute paths pointing to the build location of the AppImage by using a different shebang and some environment variables, set by the linuxdeploy-plugin-conda-hook at the AppImage start. Fixes linuxdeploy#12, fixes linuxdeploy#25 and fixes linuxdeploy#32
This removes some of the wrong, absolute paths pointing to the build location of the AppImage by using a different shebang and some environment variables, set by the linuxdeploy-plugin-conda-hook at the AppImage start. Fixes linuxdeploy#12, fixes linuxdeploy#25 and fixes linuxdeploy#32
If we bundle a script that uses
!/usr/bin/env python
, then we end up running the system-installed Python rather the bundled one. We need some sort of a wrapper to set up$PATH
at least.The text was updated successfully, but these errors were encountered: