Windows: cannot create virtualenv on different drive from system Python executable
Bug #352844 reported by
Carl Meyer
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Virtualenv |
New
|
Undecided
|
Unassigned |
Bug Description
I'm not a Windows user, so I could be missing something, but this is what I'm seeing (ran into it trying to get the pip test suite running on Windows):
S:\>virtualenv --no-site-packages blah
New python executable in blah\Scripts\
ERROR: The executable blah\Scripts\
ERROR: It thinks sys.prefix is 'c:\\python25' (should be 's:\\blah')
ERROR: virtualenv is not compatible with this system or executable
S:\>c:
C:\>virtualenv --no-site-packages yo
New python executable in yo\Scripts\
Installing setuptools.
To post a comment you must log in.
I had the same problem.
I fixed it by reinstalling Python2.6. The difference is that the first time (when virtualenv didn't work) I had installed it with the option "Only for this user", while the next time (when it worked) I reinstalled Python with the option "For all users".