How to source virtualenv activate in a Bash script

Question

How do you create a Bash script to activate a Python virtualenv   I have a directory structure like    env     bin         activate            other virtualenv files    src     shell sh        my code      I can activate my virtualenv by   user localhost src        env bin activate   env user localhost src    However  doing the same from a Bash script does nothing   user localhost src  cat shell sh    bin bash       env bin activate user localhost src    shell sh user localhost src     What am I doing wrong

User · Answer

You should call the bash script using source.

Here is an example:

#!/bin/bash
# Let's call this script venv.sh
source "<absolute_path_recommended_here>/.env/bin/activate"

On your shell just call it like that:

> source venv.sh

Or as @outmind suggested: (Note that this does not work with zsh)

> . venv.sh

There you go, the shell indication will be placed on your prompt.

User · Answer

When I was learning venv I created a script to remind me how to activate it      bin sh   init venv sh if   -d    bin    then   echo   info  Ctrl d to deactivate    bash -c    bin activate  exec  usr bin env bash --rcfile  lt  echo  PS1    venv    PS1      -i  fi   This has the advantage that it changes the prompt

User · Answer

Sourcing runs shell commands in your current shell   When you source inside of a script like you are doing above  you are affecting the environment for that script  but when the script exits  the environment changes are undone  as they ve effectively gone out of scope   If your intent is to run shell commands in the virtualenv  you can do that in your script after sourcing the activate script   If your intent is to interact with a shell inside the virtualenv  then you can spawn a sub-shell inside your script which would inherit the environment

User · Answer

Although it doesn t add the    env   prefix to the shell prompt  I found this script works as expected      bin bash script dir  dirname  0  cd  script dir  bin bash -c        env bin activate  exec  bin bash -i    e g   user localhost   src  which pip  usr local bin pip user localhost   src  which python  usr bin python user localhost   src    shell user localhost   src  which pip    env bin pip user localhost   src  which python    env bin python user localhost   src  exit exit

User · Answer

What does sourcing the bash script for    If you intend to switch between multiple virtualenvs or enter one virtualenv quickly  have you tried virtualenvwrapper  It provides a lot of utils like workon venv  mkvirtualenv venv and so on  If you just run a python script in certain virtualenv  use  path to venv bin python script py to run it

User · Answer

When you source  you re loading the activate script into your active shell   When you do it in a script  you load it into that shell which exits when your script finishes and you re back to your original  unactivated shell   Your best option would be to do it in a function  activate              env bin activate     or an alias  alias activate        env bin activate    Hope this helps

User · Answer

Here is the script that I use often  Run it as   source script name     bin bash -x PWD  pwd   usr local bin virtualenv --python python3 venv echo  PWD activate             PWD venv bin activate    activate

User · Answer

You can also do this using a subshell to better contain your usage - here s a practical example      bin bash  commandA --args    Run commandB in a subshell and collect its output in  VAR   NOTE    - PATH is only modified as an example    - output beyond a single value may not be captured without quoting    - it is important to discard  or separate  virtualenv activation stdout      if the stdout of commandB is to be captured   VAR        PATH   opt bin foo  PATH         path to activate  gt   dev null    activate virtualenv     commandB    tool from  opt bin  which requires virtualenv      Use the output from commandB later commandC   VAR    This style is especially helpful when   a different version of commandA or commandC exists under  opt bin commandB exists in the system PATH or is very common these commands fail under the virtualenv one needs a variety of different virtualenvs

User · Answer

You should use multiple commands in one line  for example   os system    Projects virenv bin activate  amp  amp  python Projects virenv django-project manage py runserver     when you activate your virtual environment in one line  I think it forgets for other command lines and you can prevent this by using multiple commands in one line  It worked for me

[python] How to source virtualenv activate in a Bash script

Examples related to python

Examples related to bash

Examples related to virtualenv