1) I installed virtualenv using pip.
2) I ran the command virtualenv venv
3) Then I ran source venv/bin/activate
but it says that there is no s
I solved the similar problem running python3.7 -m venv venv
, you can change for your version of python that is installed in your enviroment.
I double it is caused by some networking issue, I run it twice to get 'activate' script installed. Maybe first it can't connect to some source so it just abort installation.
I solved a similar problem by naming it venv2 when I ran virtualenv. I already had a virtual environment named venv for another project. This allowed me to proceed.
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. maybe you can have more try.
I experienced this problem when using the --upgrade
option. Removed the option, and all ran as expected.