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
#! /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)
/root /environments bashScript.bash script.py /random directories /name_Env /bin activate
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.