-
Notifications
You must be signed in to change notification settings - Fork 133
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
Cannot run anything installed by pipsi (module not found) #144
Comments
I'm running into the same problem. The hashbang inserted into the bin script is pointing to the system python binary rather than the binary in the associated virtualenv. I can manually change the hashbangs in the bin directory to make it execute on the correct python, but other functions like |
I also noticed that it's falsely warning that ~/.local/bin is not on my path. It looks like the command_exists function is improperly using subprocess.call and passing the cmd name without a full path. All other calls to subprocess.call are properly passing full paths. In order to not pass a full path you'll want to pass it as a string with shell=True. Alternatively, I think it would be more direct to use find_executable:
Changing command_exists removed the incorrect warning, but did not fix the problems listed in this issue |
This seems to be the same issue as #118. I've tried a fix previously, but it wasn't that straightforward. I have some time now, so I'll look into it again. |
this seems to be an issue with using venv, as it needs a different logic to find the real python for fixing scripts - im not sure if/when i find time to look at it |
This has been fixed for me in #142, maybe you can check if it works with current master, and close if it does? |
I installed pipsi on my macbook and found out two problems, which should be probably split into two issues, one is that I cannot upgrade pipsi
After installation
PATH
The text was updated successfully, but these errors were encountered: