Use the activate script in the Scripts directory of your virtual environment: > venv\Scripts\activate This will activate your virtual environment and your terminal will look like this depending on the directory you’re in: (venv) C:\Users\acer\Desktop> I hope this helps!
Strangely, I ran into this when I tried to create a virtualenv with a name that already existed. Solution to remove the old and create a new one: rmvirtualenv old-one mkvirtualenv new-one
execute_manager deprecated in Django 1.4 as part of the project layout refactor and was removed in 1.6 per the deprecation timeline: https://docs.djangoproject.com/en/1.4/internals/deprecation/#id3 To fix this error you should either install a compatible version of Django for the project or update the manage.py to new style which does not use execute_manager: https://docs.djangoproject.com/en/stable/releases/1.4/#updated-default-project-layout-and-manage-py Most likely if your … Read more
My problem was that i recently moved my project with virtualenv to another location, due to this activate script had wrong VIRTUAL_ENV path. $ cat path_to_your_env/bin/activate … # some declarations VIRTUAL_ENV=”/path_to_your_env/bin/python” # <– THIS LINE export VIRTUAL_ENV … # some declarations To fix this, just update VIRTUAL_ENV in activate script. Also you maybe need to … Read more
You’re probably using bash so just add these 3 lines to ~/.bash_profile: $ cat >> ~/.bash_profile export WORKON_HOME=$HOME/.virtualenvs export PROJECT_HOME=$HOME/directory-you-do-development-in source /usr/local/bin/virtualenvwrapper.sh ^D where ^D means you type Control+D (EOF). Then either close your terminal window and open a new one, or you can “reload” your .bash_profile like this: $ source ~/.bash_profile
virtualenv helpers for Windows command shell: virtualenvwrapper-win is a set of DOS-style batch files (doesn’t work in PowerShell). env.py is a single Python2 script (blog post).
If you are working on a custom PS1 (as I when found out this issue), I recommend you to disable prompt change, use export VIRTUAL_ENV_DISABLE_PROMPT=1 (see virtualenv docs), and make your own virtualenv prompt in order to add to your PS1. See this snippet that I’ve used: function virtualenv_info(){ # Get Virtual Env if [[ … Read more
You can use the lsvirtualenv, in which you have two options “long” or “brief”: “long” option is the default one, it searches for any hook you may have around this command and executes it, which takes more time. “brief” just take the virtualenvs names and prints it. brief usage: $ lsvirtualenv -b long usage: $ … Read more
Try reinstalling pip and then reinstalling virtualenvwrapper (I had to go through these steps after upgrading to Mavericks): $ sudo easy_install pip $ sudo pip install –upgrade virtualenvwrapper
Hopefully this is along the lines you are imagining. I attempted to simplify my solution and remove some things you likely do not need. The advantages of this method are: Single button press to launch a SublimeREPL with correct interpreter and run a file in it if desired. After setting the interpreter, no changes or … Read more