Activating a VirtualEnv using a shell script doesn't seem to work

Question

I tried activating a VirtualEnv through a shell script like the one below but it doesn\'t seem to work,

#!/bin/sh
source ~/.virtualenvs/pinax-env/bin/activa         


        

Answer 1

On Mac OS X your proposals seems not working.

I have done it this way. I'am not very happy with solution, but share it anyway here and hope, that maybe somebody will suggest the better one:

In activate.sh I have

echo 'source /Users/andi/.virtualenvs/data_science/bin/activate'

I give execution permissions by: chmod +x activate.sh

And I execute this way:

`./activate.sh`

Notice that there are paranthesis in form of ASCII code 96 = ` ( Grave accent )

Answer 2

In my case, Ubuntu 16.04, the methods above didn't worked well or it needs much works.

I just made a link of 'activate' script file and copy it to home folder(or $PATH accessible folder) and renamed it simple one like 'actai'.

Then in a terminal, just call 'source actai'. It worked!

Answer 3

TLDR

Must run the .sh script with source instead of the script solely

source your-script.sh

and not your-script.sh

Details

sh is not the same as bash (although some systems simply link sh to bash, so running sh actually runs bash). You can think of sh as a watered down version of bash. One thing that bash has that sh does not is the "source" command. This is why you're getting that error... source runs fine in your bash shell. But when you start your script using sh, you run the script in an shell in a subprocess. Since that script is running in sh, "source" is not found.

The solution is to run the script in bash instead. Change the first line to...

#!/bin/bash

Then run with...

./virtualenv_activate.sh

...or...

/bin/bash virtualenv_activate.sh

Edit:

If you want the activation of the virtualenv to change the shell that you call the script from, you need to use the "source" or "dot operator". This ensures that the script is run in the current shell (and therefore changes the current environment)...

source virtualenv_activate.sh

...or...

. virtualenv_activate.sh

As a side note, this is why virtualenv always says you need to use "source" to run it's activate script.  

Answer 4

For me best way work as below.

Create start-my-py-software.sh and pest below code

#!/bin/bash
source "/home/snippetbucket.com/source/AIML-Server-CloudPlatform/bin/activate"
python --version
python /home/snippetbucket.com/source/AIML-Server-CloudPlatform/main.py

Give file permission to run like below.

chmod +x start-my-py-software.sh

Now run like below

.start-my-py-software.sh

and that's it, start my python based server or any other code.

ubuntu #18.0

Answer 5

source is an builtin shell command in bash, and is not available in sh. If i remember correctly then virtual env does a lot of path and environment variables manipulation. Even running it as bash virtualenv_blah.sh wont work since this will simply create the environment inside the sub-shell.

Try . virtualenv_activate.sh or source virtualenv_activate.sh this basically gets the script to run in your current environment and all the environment variables modified by virtualenv's activate will be available.

HTH.

Edit: Here is a link that might help - http://ss64.com/bash/period.html