'Can not activate a virtualenv in GIT bash mingw32 for Windows
When I try to activate my virtualenv from GIT bash mingw32 I do not get the expected response.
NOTE: py is the folder for Python projects in my Google Drive folder. hy is the virtualenv folder that was made when I ran virtualenv --distribute hy.
s3z@s3z ~/Google Drive/py/hy
$ Scripts/activate
So you see, there is no expected (hy) that appears before s3z@s3z ~/Google Drive/py/hy
s3z@s3z ~/Google Drive/py/hy
$ Scripts/activate.bat
Scripts/activate.bat: line 1: @echo: command not found
Scripts/activate.bat: line 4: syntax error near unexpected token `('
Scripts/activate.bat: line 4: `if not defined PROMPT ('
And when targeting the actual file name activate.bat I get error messages. Then I try deactivating to see what happens cause I thought maybe virtualenv was activated but hidden.
s3z@s3z ~/Google Drive/py/hy
$ Scripts/deactivate.bat
Scripts/deactivate.bat: line 1: @echo: command not found
Scripts/deactivate.bat: line 3: syntax error near unexpected token `('
Scripts/deactivate.bat: line 3: `if defined _OLD_VIRTUAL_PROMPT ('
s3z@s3z ~/Google Drive/py/hy
$ Scripts/deactivate
sh.exe": Scripts/deactivate: No such file or directory
Any ideas?
Solution 1:[1]
On Windows10, you could go in the directory of your virtualenv where the Scripts folder is placed then enter the below command
source ./Scripts/activate
Note the .(dot) without this it was giving error to me when I use it like above mentioned then the solution provided by Pierre worked for me.
Solution 2:[2]
How to activate then deactivate a venv with Git Bash
To access your python in Windows 10, you need to add the .exe when creating the virtual environment.
$ python.exe -m venv Scripts
Then you can move into the Scripts folder you created for the virtual environment.
$ cd Scripts/
Now you have to call on it to activate the virtual environment.
$ source ./Scripts/activate
When you are done you just deactivate the virtual environment.
$ deactivate

Solution 3:[3]
I had the same error:
in your bash run, this commend: source venv/Scripts/activate
then check if it works using this commend: pip -V
I hope that is useful.
Solution 4:[4]
Solution 5:[5]
Danyal Abbasi@DESKTOP-7I43AM4 MINGW64 /e/Django-projects/studybudproject/studybud/Scripts
$ . activate
(studybud)
Danyal Abbasi@DESKTOP-7I43AM4 MINGW64 /e/Django-projects/studybudproject/studybud/Scripts
$ deactivate
Danyal Abbasi@DESKTOP-7I43AM4 MINGW64 /e/Django-projects/studybudproject/studybud/Scripts
$
Solution 6:[6]
I recently had this problem and i found the solution for this. after you have done
$ cd Scripts
after this you should just simply type
$ source activate
and this will activate your venv
to deactivate just type
$ deactivate
and you venv is deactivated
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | Aman Tandon |
| Solution 2 | |
| Solution 3 | Ayoub Aarab |
| Solution 4 | Kainix |
| Solution 5 | Danyal Muneer |
| Solution 6 | anil gurjar |

