I have this directory structure:
C:/Python/projects/
|
|__ myproject1name/
| |__project1site/
| |__myvenv/
|
|__ myproject2name/
|__project2site/
|__myvenv/
To activate myvenv I digit C:/python/projects/myproject1name/myvenv/scripts/activate
It works but it's boring so I want to use virtualenvwrapper-win
I installed it inside myvenv (that is with myvenv active)... I think it's an error so I installed again globally. Right?
Anyway it doesn't works (workon command unknow).
I think I should set WORKON_HOME enviroment variable. I see two ways:
1) use the default %USERPROFILE%Envs
2) set WORKON_HOME=C:/Python/projects/ but then each project should have a different named env? or maybe it choose based on the path from where I call workon?
Anyway I choose to create a directory C:/Python/envs where to put each env and moved C:/Python/projects/myproject1name/myvenv in this directory and renamed it myproject1name so now I have:
C:/Python/envs/myproject1name
I set WORK_HOME=C:/Python/envs
lsvirtualenvs give
dir /b /ad "C:PythonEnvs"
=============================
myproject1name
and workon myproject1name gives:
(myvenv) C:Pythonprojectsmyproject1nameproject1site>
so it looks active but pip list give only the package globally installed and manage.py runserver can find django (for exemple). And why is it called myvenv? Shouldn't be myproject1name?
Maybe I can't just move and rename myvenv, or what? Where do you think I should store the myvenvs?
I'm using Python3.5, Windows7