flask

Question

Having trouble with virtualenv on Windows 7.

I run:

virtualenv _testenv

It returns:

Traceback (most recent call last):
  File "C:\Python27\Scripts\virtualenv-script.py", line 9, in <module>
    load_entry_point('virtualenv==1.5.2', 'console_scripts', 'virtualenv')()
  File "C:\Python27\lib\site-packages\virtualenv.py", line 558, in main
    prompt=options.prompt)
  File "C:\Python27\lib\site-packages\virtualenv.py", line 647, in create_environment
    site_packages=site_packages, clear=clear))
  File "C:\Python27\lib\site-packages\virtualenv.py", line 771, in install_python
    copy_required_modules(home_dir)
  File "C:\Python27\lib\site-packages\virtualenv.py", line 725, in copy_required_modules
    dst_filename = change_prefix(filename, dst_prefix)
  File "C:\Python27\lib\site-packages\virtualenv.py", line 710, in change_prefix
    (filename, prefixes)
AssertionError: Filename c:\Python27\Lib\os.py does not start with any of these prefixes: ['C:\\Python27']

I have the following environment variables:

PYTHONHOME=C:\Python27
PYTHONPATH=c:\Python27;c:\Python27\Lib
PYTHONSTARTUP=C:\Users\Larry\.pythonrc
PATH=%PYTHONHOME%\;%PYTHONHOME%\Scripts;etc

Installed ActiveState Python:

ActivePython 2.7.2.5 (ActiveState Software Inc.) based on
Python 2.7.2 (default, Jun 24 2011, 12:21:10) [MSC v.1500 32 bit (Intel)] on win32

I updated the PYTHONPATH=C:\Python27;C:\Python27\Lib Still looking for a solution, I found and removed AppData/Python*. Reinstalled Python and now have a different error:

C:\xbz>virtualenv _t
PYTHONHOME is set.  You *must* activate the virtualenv before using it
Overwriting _t\Lib\site.py with new content
New python executable in _t\Scripts\python2.7.exe
Not overwriting existing python script _t\Scripts\python.exe (you must use _t\Scripts\python2.7.exe)
Overwriting _t\Lib\distutils\__init__.py with new content
Installing setuptools..............
  Complete output from command C:\xbz\_t\Scripts\python2.7.exe -c "#!python
\"\"\"Bootstrap setuptoo...


" --always-copy -U setuptools:
  Traceback (most recent call last):
  File "<string>", line 278, in <module>
  File "<string>", line 210, in main
  File "<string>", line 132, in download_setuptools
  File "C:\Python27\Lib\urllib2.py", line 94, in <module>
    import httplib
  File "C:\Python27\Lib\httplib.py", line 71, in <module>
    import socket
  File "C:\Python27\Lib\socket.py", line 47, in <module>
    import _socket
ImportError: No module named _socket
----------------------------------------
...Installing setuptools...done.
Traceback (most recent call last):
  File "C:\Python27\Scripts\virtualenv-script.py", line 9, in <module>
    load_entry_point('virtualenv==1.5.2', 'console_scripts', 'virtualenv')()
  File "C:\Python27\lib\site-packages\virtualenv.py", line 558, in main
    prompt=options.prompt)
  File "C:\Python27\lib\site-packages\virtualenv.py", line 654, in create_environment
    install_setuptools(py_executable, unzip=unzip_setuptools)
  File "C:\Python27\lib\site-packages\virtualenv.py", line 384, in install_setuptools
    _install_req(py_executable, unzip)
  File "C:\Python27\lib\site-packages\virtualenv.py", line 360, in _install_req
    cwd=cwd)
  File "C:\Python27\lib\site-packages\virtualenv.py", line 624, in call_subprocess
    % (cmd_desc, proc.returncode))
OSError: Command C:\xbz\_t\Scripts\python2.7.exe -c "#!python
\"\"\"Bootstrap setuptoo...




" --always-copy -U setuptools failed with error code 1

I hacked Lib/socket.py and inserted:

import sys
sys.path = ['', 'C:\\Python27\\lib\\site-packages\\dotcloud-0.3.1-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\dotcloud.cli-0.3.1-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\flask-0.7dev_20110622-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\werkzeug-0.6.2-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\gunicorn-0.12.2-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\wtforms-0.6.3-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\repoze.browserid-0.3-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\paste-1.7.5.1-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\django_pjax-1.0-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\paramiko-1.7.7.1-py2.7.egg', 'C:\\Python27\\lib\\site-packages\\pycrypto-2.4.1-py2.7-win32.egg', 'C:\\Python27', 'C:\\Python27\\Lib', 'C:\\Windows\\system32\\python27.zip', 'C:\\Python27\\DLLs', 'C:\\Python27\\lib\\plat-win', 'C:\\Python27\\lib\\lib-tk', 'C:\\Python27\\lib\\site-packages', 'C:\\Python27\\lib\\site-packages\\PIL', 'C:\\Python27\\lib\\site-packages\\win32', 'C:\\Python27\\lib\\site-packages\\win32\\lib', 'C:\\Python27\\lib\\site-packages\\Pythonwin', 'C:\\Python27\\lib\\site-packages\\setuptools-0.6c11-py2.7.egg-info', 'C:\\Python27\\Scripts', 'C:\\Python27\\Lib\\site-packages\\django\\bin']

Above

import _socket

The reason was that I was able to import socket from straight python prompt! So stuffed my existing path. I haven't narrowed down exactly which directory made it happy. It at least will reveal to someone else why I am getting the error without it.

Ideas? Suggestions? Thank you. :)

I hacked Lib/socket.py and inserted:

import sys
sys.path.append('C:\\Python27\\DLLs')

Above

import _socket

Check with this question stackoverflow.com/questions/4527958/python-virtualenv-questions — Zain Khan, Dec 31 '11 at 14:48
Still looking for a solution, I found and removed AppData/Python*. Reinstalled Python and now have a different error. See updated original question. — Larry Eitel, Jan 4 '12 at 21:30
I found a workaround involving hacking C:\Python27\Lib\socket.py. See about. — Larry Eitel, Jan 25 '12 at 23:36
I've filed this as a bug: github.com/pypa/virtualenv/issues/815. — Martijn Pieters♦, Nov 3 '15 at 16:45

101 · Answer 1 · 2015-04-29 05:28:38Z

up vote 11 down vote

Try to set PYTHONPATH to PYTHONPATH=C:\Python27;C:\Python27\Lib (uppercase C at the start).

This can be done at the command prompt by typing set PYTHONPATH=C:\Python27;C:\Python27\Lib.

PYTHONPATH will revert back to whatever it previously was once that command prompt window is closed.

edited Apr 29 '15 at 5:28

101

3,450 2 11 32

answered Dec 31 '11 at 14:46

ojii

3,517 1 10 23

Sorry but that didn't help. :( – Larry Eitel Jan 1 '12 at 23:22

It did this time. :) Thank you :) – Larry Eitel Oct 9 '12 at 20:45

add a comment

Mike Davlantes · Answer 2 · 2015-02-04 17:35:27Z

3 year old question, but hopefully this answer can still help someone. Rather than setting the environment variables (which mysteriously didn't work for me), you can pass the path to your Python installation when setting up the virtual environment. In Windows, you have to path out to python.exe, but it seems that in Linux/OS X you just path to the folder. Examples:

Windows:

virtualenv -p <PATH TO PYTHON.EXE> venv

Linux/Mac:

virtualenv -p </user/path/to/python> venv

Both create a virtual environment in subfolder "venv" in current directory.

David Marble · Answer 3 · 2012-04-03 01:31:19Z

up vote 4 down vote

For the _socket error, change your pythonpython path to:

PYTHONPATH=C:\Python27;C:\Python27\Lib;C:\Python27\DLLs

answered Apr 3 '12 at 1:31

David Marble

1,003 12 8

add a comment

Abhijit · Answer 4 · 2011-12-31 14:52:30Z

Its strange but from the error message

AssertionError: Filename c:\Python27\Lib\os.py does not start with any of these prefixes: ['C:\\Python27']

It seems, it expects the path-name for the file os.py to start with upper case 'C' and the prefix sanity check is case sensitive.

As the path to the library is derived from PYTHONPATH and in your case the drive letter is in lower case, it seems logical to change it to upper case to resolve the issue.

like

PYTHONPATH=C:\Python27;C:\Python27\Lib

I had this same issue. Just to reiterate, you have to look at the error message and make sure that the /case/ of all the letters in the path setting match the error message. Also, after you change the PATH settings, you have to start a new command prompt before the new settings will be used. — hazzey, Jul 18 '14 at 13:30

Jesse · Answer 5 · 2012-07-10 16:47:16Z

I hate "summary" answers, but as I just went through a very similar issue I thought I would post my solution here as well which draws from several of these answers.

The assert error was caused because I did not have a PYTHONPATH environment variable setup.

The socket error was caused because I did not include the PythonXX\DLLs folder.

The full PYTHONPATH environment variable should look follows:

PYTHONPATH=C:\Python27;C:\Python27\Lib;C:\Python27\DLLs

user3930993 · Answer 6 · 2016-04-20 13:51:09Z

up vote 1 down vote

I have added

if is_win:    
        prefixes.append('C:\PYTHON27')

to virtualenv.py and it works.

answered Apr 20 at 13:51

user3930993

11 1

add a comment

Sabuncu · Answer 7 · 2012-05-12 11:27:25Z

I also ran into this problem on Windows 7. My Python27 installation was under C:\Program Files, which obviously contains a space in the path. So, on a separate Windows 7 system that did not contain Python, I did a fresh install of Python27 under C:\Python27 (the default installation path), followed by an install of setuptools (for easy_install).

Afterwards, I was able to install virtualenv CLEANLY without the above assertion error (I used easy_install).

I know that the OP's system is already using the default path, but I thought I would add my experience here as a possible solution for certain specific cases.

Jim Gray · Answer 8 · 2013-01-02 05:29:13Z

This issue is presumably a hangover from other more case-sensitive file systems.

Complete solution:

Read the error message from virtualenv. Remember the part where it says "does not start with any of these prefixes: ['C:\\Python27']".
Edit PYTHONPATH, or create it if you don't have one (Start+Break, Advanced system settings, Environment Variables). It shouldn't matter if it's a user variable or a system variable, unless you plan to switch user accounts.
Make the case match the error message. BOTH the drive letter AND the folder name must match (presumably intermediate folders as well, if you didn't install to C:\Python27). You can ignore the double backslash, one is fine.

The only change I made to fix the bug was as follows. The change should take effect for any new command / terminal sessions (close your open cmd.exe / powershell / etc. windows).

Old state: PYTHONPATH = C:\PYTHON27;C:\PYTHON27\LIB;C:\PYTHON27\DLLS
New state: PYTHONPATH = C:\Python27;C:\Python27\LIB;C:\Python27\DLLS

If you have any other items in your PYTHONPATH, you might as well change those too, but it probably won't affect virtualenv's ability to run.

LICF · Answer 9 · 2015-06-14 05:47:49Z

Change "virtualenv.py" --> change_prefix with:

def change_prefix(filename, dst_prefix):
  ...
 prefixes = sorted(prefixes, key=len, reverse=True)
 filename = str(os.path.abspath(filename))[0].lower() + str(os.path.abspath(filename))[1:]
 for src_prefix in prefixes:
    if filename.startswith(src_prefix):
        _, relpath = filename.split(src_prefix, 1)
        if src_prefix != os.sep: # sys.prefix == "/"
            assert relpath[0] == os.sep
            relpath = relpath[1:]
        return join(dst_prefix, relpath)
 assert False, "Filename %s does not start with any of these prefixes: %s" % \
    (filename, prefixes)

  ...

user405 · Answer 10 · 2015-12-03 21:52:29Z

I had the same assertion error from a slightly different cause. The error was does not start with any of these prefixes: ['C:\\python27'] and note the lowercase "p". The actual folder names all use capital-P Python27. All the prefixes in PTYHONPATH were correct. However I had entered the PYTHONHOME variable as C:\python27 and although this was fine for Python, it caused the error in virtualenv.

score 0 · Answer 11

This is an error already submitted to the Python development team:https://github.com/pypa/virtualenv/pull/697

In the meanwhile why not just change the Python installation folder name to (ptyhon27) to make the assertion work, or if you feel more confortable with that just reinstall python using the alternative location. It works with no issue.

101 · Answer 12 · 2015-04-29 05:28:38Z

up vote 11 down vote

Try to set PYTHONPATH to PYTHONPATH=C:\Python27;C:\Python27\Lib (uppercase C at the start).

This can be done at the command prompt by typing set PYTHONPATH=C:\Python27;C:\Python27\Lib.

PYTHONPATH will revert back to whatever it previously was once that command prompt window is closed.

edited Apr 29 '15 at 5:28

101

3,450 2 11 32

answered Dec 31 '11 at 14:46

ojii

3,517 1 10 23

Sorry but that didn't help. :( – Larry Eitel Jan 1 '12 at 23:22

It did this time. :) Thank you :) – Larry Eitel Oct 9 '12 at 20:45

add a comment

Mike Davlantes · Answer 13 · 2015-02-04 17:35:27Z

3 year old question, but hopefully this answer can still help someone. Rather than setting the environment variables (which mysteriously didn't work for me), you can pass the path to your Python installation when setting up the virtual environment. In Windows, you have to path out to python.exe, but it seems that in Linux/OS X you just path to the folder. Examples:

Windows:

virtualenv -p <PATH TO PYTHON.EXE> venv

Linux/Mac:

virtualenv -p </user/path/to/python> venv

Both create a virtual environment in subfolder "venv" in current directory.

David Marble · Answer 14 · 2012-04-03 01:31:19Z

up vote 4 down vote

For the _socket error, change your pythonpython path to:

PYTHONPATH=C:\Python27;C:\Python27\Lib;C:\Python27\DLLs

answered Apr 3 '12 at 1:31

David Marble

1,003 12 8

add a comment

Abhijit · Answer 15 · 2011-12-31 14:52:30Z

Its strange but from the error message

AssertionError: Filename c:\Python27\Lib\os.py does not start with any of these prefixes: ['C:\\Python27']

It seems, it expects the path-name for the file os.py to start with upper case 'C' and the prefix sanity check is case sensitive.

As the path to the library is derived from PYTHONPATH and in your case the drive letter is in lower case, it seems logical to change it to upper case to resolve the issue.

like

PYTHONPATH=C:\Python27;C:\Python27\Lib

I had this same issue. Just to reiterate, you have to look at the error message and make sure that the /case/ of all the letters in the path setting match the error message. Also, after you change the PATH settings, you have to start a new command prompt before the new settings will be used. — hazzey, Jul 18 '14 at 13:30

Jesse · Answer 16 · 2012-07-10 16:47:16Z

I hate "summary" answers, but as I just went through a very similar issue I thought I would post my solution here as well which draws from several of these answers.

The assert error was caused because I did not have a PYTHONPATH environment variable setup.

The socket error was caused because I did not include the PythonXX\DLLs folder.

The full PYTHONPATH environment variable should look follows:

PYTHONPATH=C:\Python27;C:\Python27\Lib;C:\Python27\DLLs

user3930993 · Answer 17 · 2016-04-20 13:51:09Z

up vote 1 down vote

I have added

if is_win:    
        prefixes.append('C:\PYTHON27')

to virtualenv.py and it works.

answered Apr 20 at 13:51

user3930993

11 1

add a comment

Sabuncu · Answer 18 · 2012-05-12 11:27:25Z

I also ran into this problem on Windows 7. My Python27 installation was under C:\Program Files, which obviously contains a space in the path. So, on a separate Windows 7 system that did not contain Python, I did a fresh install of Python27 under C:\Python27 (the default installation path), followed by an install of setuptools (for easy_install).

Afterwards, I was able to install virtualenv CLEANLY without the above assertion error (I used easy_install).

I know that the OP's system is already using the default path, but I thought I would add my experience here as a possible solution for certain specific cases.

Jim Gray · Answer 19 · 2013-01-02 05:29:13Z

This issue is presumably a hangover from other more case-sensitive file systems.

Complete solution:

Read the error message from virtualenv. Remember the part where it says "does not start with any of these prefixes: ['C:\\Python27']".
Edit PYTHONPATH, or create it if you don't have one (Start+Break, Advanced system settings, Environment Variables). It shouldn't matter if it's a user variable or a system variable, unless you plan to switch user accounts.
Make the case match the error message. BOTH the drive letter AND the folder name must match (presumably intermediate folders as well, if you didn't install to C:\Python27). You can ignore the double backslash, one is fine.

The only change I made to fix the bug was as follows. The change should take effect for any new command / terminal sessions (close your open cmd.exe / powershell / etc. windows).

Old state: PYTHONPATH = C:\PYTHON27;C:\PYTHON27\LIB;C:\PYTHON27\DLLS
New state: PYTHONPATH = C:\Python27;C:\Python27\LIB;C:\Python27\DLLS

If you have any other items in your PYTHONPATH, you might as well change those too, but it probably won't affect virtualenv's ability to run.

LICF · Answer 20 · 2015-06-14 05:47:49Z

Change "virtualenv.py" --> change_prefix with:

def change_prefix(filename, dst_prefix):
  ...
 prefixes = sorted(prefixes, key=len, reverse=True)
 filename = str(os.path.abspath(filename))[0].lower() + str(os.path.abspath(filename))[1:]
 for src_prefix in prefixes:
    if filename.startswith(src_prefix):
        _, relpath = filename.split(src_prefix, 1)
        if src_prefix != os.sep: # sys.prefix == "/"
            assert relpath[0] == os.sep
            relpath = relpath[1:]
        return join(dst_prefix, relpath)
 assert False, "Filename %s does not start with any of these prefixes: %s" % \
    (filename, prefixes)

  ...

user405 · Answer 21 · 2015-12-03 21:52:29Z

I had the same assertion error from a slightly different cause. The error was does not start with any of these prefixes: ['C:\\python27'] and note the lowercase "p". The actual folder names all use capital-P Python27. All the prefixes in PTYHONPATH were correct. However I had entered the PYTHONHOME variable as C:\python27 and although this was fine for Python, it caused the error in virtualenv.

score 0 · Answer 22

This is an error already submitted to the Python development team:https://github.com/pypa/virtualenv/pull/697

In the meanwhile why not just change the Python installation folder name to (ptyhon27) to make the assertion work, or if you feel more confortable with that just reinstall python using the alternative location. It works with no issue.

flask

virtualenv on windows 7 returns AssertionError

11 Answers

virtualenv on windows 7 returns AssertionError

11 Answers