'Issue with activating virtualenv

I installed python environment by means of commands:

SYS_INSTALL="apt-get install -y"
PIP_INSTALL="pip install"

# Be sure to install setuptools before pip to properly replace easy_install.
$SYS_INSTALL git 
$SYS_INSTALL python-dev
$SYS_INSTALL python-setuptools
$SYS_INSTALL python-pip
$PIP_INSTALL virtualenv

also was able to create new virtual environment:

virtualenv .env

However, after running a command like:

. .env/bin/activate

I got

-bash: .env/bin/activate: No such file or directory

After reviewing folder .env/bin I found only one python file. Whole list of files here:

.env/lib:
python2.7

.env/include:
python2.7

.env/bin:
python

What is the issue here?

SOLUTION add --always-copy

virtualenv .env --always-copy

bashpython-2.7pipubuntu-14.04virtualenv


Solution 1:[1]

The accepted answer is incomplete! The suggested code left out your error, but didn't comment on it.

The command . .env/bin/activate would indeed do the same as source on the file activate in the folder .env/bin. In fact, apparently the command "source" is an alias for the command ".", and not the other way around. Note that . here has a space after it, and used differently from the . discussed below (which makes files and folders hidden).

What I notice is that you are calling your folder .env, which is not standard practice. Files and folders preceded by . are made "hidden" by Mac OS X. Standard practice is to call a virtual environment directory env or venv, and to call the virtual environment specification file .env.

So, if your spec file is called .env and your virtual environment directory is called env, you can run either

source env/bin/activate or . env/bin/activate.

Solution 2:[2]

For me it works when I do these steps:

  • Go to the directory/folder that you want

  • run virtualenv .env

  • then run source .env/bin/activate

Solution 3:[3]

I had the same issue and the following steps resolved it:

$mkdir annotateNLP
$cd annotateNLP
$python -m venv env
$source env/Scripts/activate

Solution 4:[4]

you forgot to include source before activating command is
source env/bin/activate

this question is similar to your's virtualenv is not compatible with this system or executable where it creates virtualenv but,python file instead of activate in bin

Solution 5:[5]

After going to your virtual environment folder .\Scripts\activate.

Solution 6:[6]

Try these commands in the terminal:

$ mkdir djangoapp
$ cd djangoapp
$ python3 -m venv myvenv
$ source myvenv/bin/activate

You can't go straight into activate command without first creating your virtual environment.

Solution 7:[7]

I was facing this same issue. I uninstalled the virtualenv in Ubuntu and then I installed it again. After this nonsense, it works and now I am able to activate my virtualenv through -$source py3/bin/activate.

Solution 8:[8]

In my case, I need to install

sudo apt-get install python3-venv

Solution 9:[9]

If installed venv on a Windows machine, run this command (assuming you are in the working directory that has your venv folder):

  • In bash terminal: source venv/Scripts/activate
  • In cmd terminal: venv\Scripts\activate

where venv is the folder name for your virtual environment

Solution 10:[10]

For windows using git bash, run the below command:-

source env\Scripts\activate

Solution 11:[11]

$ virtualenv env
$ cd env/Scripts/
$ . activate

Related Questions