mijorus/gearlever

Calling python -m venv for some reason uses a gearlever appimage instead of python as its binary

Closed this issue · 1 comments

I was running python -m venv test which gave me the error Error: Command '['[path]/test/abcd/bin/gearlever_digikam_0e275a.appimage', '-m', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1.
And sure enough, the python binaries within the venv are actually the appimage.
Running most of the other modules also tries to run the appimage.
For example python -m test runs the appimage from cli, python -m ensurepip actually runs python. Calling just python works fine too.
Actually python -m seems to get replaced by the path of one of my appimages.

Also, this only happens when using my normal shell zsh. Using bash (or another zsh invoked through cli), without any of my normal aliases or variables, does not have that error. Somehow, some command shenanigan needs to interfere with the python -m command and replace something with appimage variables. What variables does Gearlever set?

Using python3.11, Ubuntu 23.10.

Further investigation makes it look like a problem with zsh itself, not gearlever.