I'm normally a unix/Mac person, so I'm not exactly sure how this might be related, but one of my users is on a windows box (windows 7?) running via cmd command line.
I have a virtualenv set up for windows, on this one system (other computers work fine) I can start the virtualenv (activate.bat) and when I run python from within the venv/Scripts directory, things look fine. my sys.path is correct.
When I cd .., and run python again (or run python from anywhere else), the sys.path is what sys.path would be if I weren't in the virtualenv.
I still have the (venv) prepended to my prompt, so venv THINKS it's still active...
correct sys.path:
['', 'C:\\Windows\\system32\\python27.zip',
'C:\\Users\\dellam\\Dropbox (CEP)\\users\\brianp\\course\\CYAN\\venv\\DLLs',
'C:\\Users\\dellam\\Dropbox (CEP)\\users\\brianp\\course\\CYAN\\venv\\lib',
'C:\\Users\\dellam\\Dropbox CEP)\\users\\brianp\\course\\CYAN\\venv\\lib\\plat-win',
[ETC]]
sys.path from anywhere other than venv\Scripts:
sys.path
['', 'C:\\Windows\\system32\\python27.zip', 'C:\\Python27\\DLLs',
'C:\\Python27\\lib', 'C:\\Python27\\lib\\plat-win',
'C:\\Python27\\lib\\lib-tk', 'C:\\Python27',
'C:\\Python27\\lib\\site-packages']
I'm using virtualenv correctly. At least, it works on other computers. I'm correctly creating a venv, and I'm activating it. It has the (venv) appended to my prompt. The question people are linking to explains how to use virtual env. I'm doing all of that correctly.