i have had the same problem. and what i did is just run the command virtualenv env again. And then more files were generated under directory env/bin, including the activate file. it’s so weird.
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
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
The better way is to use the full path to installed script – it will run in its virtualenv automatically: tasks: – name: install python packages pip: name={{ item }} virtualenv={{ venv }} with_items: [ buildbot ] – name: create buildbot master command: “{{ venv }}/bin/buildbot create-master ~/buildbot creates=~/buildbot/buildbot.tac”
The problem is correctly spotted by Mathijs. $ which sphinx-build /usr/local/bin/sphinx-build I solved this issue installing sphinx itself in the virtual environment. With the environment activated: $ source /home/migonzalvar/envs/myenvironment/bin/activate $ pip install sphinx $ which sphinx-build /home/migonzalvar/envs/myenvironment/bin/sphinx-build It seems neat enough.
Add following in your .bashrc or .zshrc function cd() { builtin cd “$@” if [[ -z “$VIRTUAL_ENV” ]] ; then ## If env folder is found then activate the vitualenv if [[ -d ./.env ]] ; then source ./.env/bin/activate fi else ## check the current folder belong to earlier VIRTUAL_ENV folder # if yes then … Read more
apt-get install libpq-dev helped me on debian squeeze From comments: apt-get install python-dev-is-python3
Virtualenv was created long before docker. Today, I lean towards docker instead of virtualenv for these reasons: Virtualenv still means people consuming your product need to download eggs. With docker, they get something which is “known to work”. No strings attached. Docker can do much more than virtualenv (like create a clean environment when you … Read more
You can list only packages in the virtualenv by pip freeze –local or pip list –local. This option works irrespective of whether you have global site packages visible in the virtualenv. Note that restricting the virtualenv to not use global site packages isn’t the answer to the problem, because the question is on how to … Read more
You don’t need to activate to use virtualenv it is a convenience. You can just use the virtualenv directly: virtualenv venv ./venv/bin/pip install foo Have you tried from fish using: . venv/bin/activate.fish It probably isn’t as widely used as bash so may have issues – looking at the commit history shows a recent fix: https://github.com/pypa/virtualenv/blob/master/virtualenv_embedded/activate.fish