Get alerted when assets are down, slow, or vulnerable to SSL attacks—all free for a month. Learn more

Question

activating virtualenv and running python script in bash file

I would like to know how to activate a python virtual env and running a python script inside a bash file.

When I go to my environment directory and do “source name_Env/bin/activate” (without quotes ofcourse) it activates like normal and I can run script.py without getting configparser errors. But with doing that in bash it seems like it doesnt know the path to the activate file / the activate file

The file:

#! /bin/bash
source name_Env/bin/activate
# virtualenv is now active.
#
python script.py

When i try to run it with either “source bashScript.bash” or “bash bashScript.bash” I get the errors: source: No such file or directoryctivate bash: No such file or directory line 2: name_Env/bin/activate and the python configparser error.

The weird thing is that when i type the same thing manually everything works fine but in the bash file not. Is there something wrong in the bash file has it something to do with something else?

(the reason I am using bash file is because I think you cant open a virtualenv in a cronjob but you can link to a file that opens one and runs script)

The directory

/root
	/environments
		bashScript.bash
		script.py
		/random directories
		/name_Env
			/bin
				activate
Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Jonathan Tittle • January 25, 2017

@Huskerdoggo

Generally, when sourcing a file, you want to use either ./ or the full path, so what I’d recommend is using:

#!/usr/bin/env bash

source ./name_Env/bin/activate

or

#!/usr/bin/env bash

source /root/environments/name_Env/bin/activate

Though you should also be able to use double-quotes around the source file as well.

#!/usr/bin/env bash

source "./name_Env/bin/activate"

or

#!/usr/bin/env bash

source "/root/environments/name_Env/bin/activate"

You could even set the file to a variable:

#!/usr/bin/env bash

readonly sourceFile="./name_Env/bin/activate"

source ${sourceFile}

or

#!/usr/bin/env bash

readonly sourceFile="/root/environments/name_Env/bin/activate"

source ${sourceFile}

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up