Unable to install boto3

Don’t use sudo in a virtual environment because it ignores the environment’s variables and therefore sudo pip refers to your global pip installation. So with your environment activated, rerun pip install boto3 but without sudo.

Issue with virtualenv – cannot activate

source is a shell command designed for users running on Linux (or any Posix, but whatever, not Windows). On Windows, virtualenv creates a .bat/.ps1 file, so you should run venv\Scripts\activate instead (per the virtualenv documentation on the activate script). Just run activate, without an extension, so the right file will get used regardless of whether you’re using cmd.exe or PowerShell.

What’s the difference between “virtualenv” and “-m venv” in creating Virtual environments(Python)

venv is a package shipped directly with python 3. So you don’t need to pip install anything. virtualenv instead is an independent library available at https://virtualenv.pypa.io/en/stable/ and can be install with pip. They solve the same problem and work in a very similar manner. If you use python3 I suggest to avoid an “extra” dependancy and just stick with venv Your error is … Read more

‘virtualenv’ is not recognized as an internal or external command, operable program or batch file

steps: – go to where you want create django app on that folder. then run this command on command prompt : python -m virtualenv . (eg. C:\Users\gshiv\Desktop\django>python -m virtualenv .) where django is the my folder i want run virtualenv and .(dot) indicates virtualenv install all it’s folder in django folder otherwise you can use other … Read more

bash: mkvirtualenv: command not found

Solution 1: For some reason, virtualenvwrapper.sh installed in /usr/bin/virtualenvwrapper.sh, instead of under /usr/local/bin. The following in my .bash_profile works… My install seems to work fine without sourcing virtualenvwrapper_bashrc Solution 2: Alternatively as mentioned below, you could leverage the chance that virtualenvwrapper.sh is already in your shell’s PATH and just issue a source `which virtualenvwrapper.sh`