There is another possible scenario that might get some people as well (if you have python and python3 on your system): pip3 install boto3 Note the use of pip3 indicates the use of Python 3’s pip installation vs just pip which indicates the use of Python 2’s.
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” dependency … Read more
Funny you brought this up, I just had the exact same problem. I solved it eventually, but I’m still unsure as to what caused it. Try checking your bin/pip and bin/activate scripts. In bin/pip, look at the shebang. Is it correct? If not, correct it. Then on line ~42 in your bin/activate, check to see … Read more
The virtualenv is “baked into the Python interpreter in the virtualenv”. This means you can launch python or console_scripts directly in that virtualenv and don’t need to activate the virtualenv first or manage PATH yourself.: ExecStart={{ venv_home }}/bin/fooservice –serve-in-foreground or ExecStart={{ venv_home }}/bin/python {{ venv_home }}/fooservice.py –serve-in-foreground and remove the EnvironmentFile entry. To verify that … Read more
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
If you happen to be using the venv module that comes with Python 3.3+, it supports an –upgrade option. Per the docs: Upgrade the environment directory to use this version of Python, assuming Python has been upgraded in-place python3 -m venv –upgrade ENV_DIR
Here is my workflow after creating a folder and cd‘ing into it: virtualenv venv –distribute Output: New python executable in venv/bin/python Installing distribute………done. Installing pip…………….done. And source venv/bin/activate python
I’ve found this snippet as an alternative solution. It’s a more graceful removal of libraries than remaking the virtualenv: pip freeze | xargs pip uninstall -y In case you have packages installed via VCS, you need to exclude those lines and remove the packages manually (elevated from the comments below): pip freeze | grep -v … Read more
if [[ “$VIRTUAL_ENV” != “” ]] then INVENV=1 else INVENV=0 fi // or shorter if you like: [[ “$VIRTUAL_ENV” == “” ]]; INVENV=$? EDIT: as @ThiefMaster mentions in the comments, in certain conditions (for instance, when starting a new shell – perhaps in tmux or screen – from within an active virtualenv) this check may … Read more
You do not need to activate the virtual environment while running in .bat. All you need to do is to run the python.exe file in your virtual environment. {path to virtual environment directory}/Scripts/python.exe path/to/your/file.py In Windows Task Scheduler you can specify the path in which the command prompt will open. So all you need to … Read more