-
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
Python prefix is incorrect #70
Comments
at first glance this looks like a issue on osx, i cant verify it since i don't have fit hardware |
I'm eager to find the solution, let me know what i should try out. |
right now i have no idea myself, it seels to be related to virtualenv, but im just vaugely guessing |
If the venv module is found, use it to create the virtual env, otherwise fallback to use virtualenv. An new paramater --virtualenv is available to force the use of virtualenv. It fixes the problem on OSX mitsuhiko#70
The reasons behind this problem are quite obscure, as you'll see from the fix. The necessary ingredients are Python 3, virtualenv (not venv), OS X and Homebrew. To fix the problem, you have to pop an environment variable called PYVENV_LAUNCHER before launching the subprocess. I made the following changes in
The following links provide more background: pypa/virtualenv#532 Finally, I found the initial problem with (OSX+Homebrew) Python 3.6 (most of the other links refer to 3.3 -> 3.5), and the resolution above also resolves the problem on 3.6. EDIT: finally found a more complete description of the root cause: https://bugs.python.org/issue22490#msg227579 |
@cjrh can you submit a pr? personally i am handing pipsi in a minimal workload on me mode, and a pr is far simpler to manage than needing to recreate a patch based on instructions (even if in this case it does look reasonably trivial i also do wonder if there is any way to create a automated test for that case |
@RonnyPfannschmidt The problem goes away if #71 is merged, and I think that's the better solution than the hacky env var change above. |
If the venv module is found, use it to create the virtual env, otherwise fallback to use virtualenv. An new paramater --virtualenv is available to force the use of virtualenv. Fixes mitsuhiko#70
Hi,
When I do a pipsi install, the python prefix in the scripts first line is incorrect and point to the system python. I'm trying to figure why, but I can't find an explanation. Do you have any pointer where I should look? I'm using ZSH on OSX if that matters somehow.
This is the output with
virtualenv -v
andpip -v -v -v
https://gist.github.com/marcaurele/ef8dd46b802bd0cde77aIf I do it manually, of course it works (virtualenv & pip), but that's not the point.
The text was updated successfully, but these errors were encountered: