与其在虚拟环境特定的shebangs上瞎折腾，还不如在crontab上预先加上PATH。

在激活的virtualenv中，运行这三个命令，python脚本就可以工作了:

$ echo "PATH=$PATH" > myserver.cron
$ crontab -l >> myserver.cron
$ crontab myserver.cron

crontab的第一行现在应该是这样的:

PATH=/home/me/virtualenv/bin:/usr/bin:/bin:  # [etc...]

如果你在使用python，并且使用Conda虚拟环境，其中你的python脚本包含shebang #!/usr/bin/env python:

* * * * * cd /home/user/project && /home/user/anaconda3/envs/envname/bin/python script.py 2>&1

此外，如果你想在你的脚本中捕获任何输出(例如打印，错误等)，你可以使用以下命令:

* * * * * cd /home/user/project && /home/user/anaconda3/envs/envname/bin/python script.py >> /home/user/folder/script_name.log 2>&1

我也遇到过同样的问题，并花了很多时间去解决它。 这里没有一个解决方案对我有帮助，所以我分享了对我有用的方法:

在项目目录中打开一个新文件“pick_name.sh”。 在"pick_name.sh"文件中，写入并保存以下代码行:

#!/bin/bash
source /YOUR_VIRTUAL_ENV_PATH/bin/activate
export PYTHONPATH="${PYTHONPATH}:/PATH_TO_CUSTOM_MODULE_YOU_CREATED**OPTIONAL**"
export PYTHONPATH="${PYTHONPATH}:/PATH_TO_ANOTHER_CUSTOM_MODULE_YOU_CREATED**OPTIONAL**"
cd /PATH_TO_DIR_STORING_FILE_NAME.PY
python file_name.py

转到/var/spool/cron/crontabs(或到您的cron管理文件所在的位置)并打开“根”文件。 将这些行添加到crontab文件夹中的根文件中:

# m h  dom mon dow   command
* * * * * /PATH_TO_DIR_WHERE_PICK_NAME.SH_SITS/pick_name.sh >> /YOUR_PROJECT_DIR/cron_output.txt 2>&1

注:

This command (section 4.) will run the "pick_name.sh" file. In this example it runs every minute, so make sure you change it according to your needs. It writes all logs to a log file called "cron_ouput". No need to create the file before, it will be created automatically. Make sure to replace all paths (I wrote them in capital letters) to your paths. You can change file names, if so, make sure to change it in all appearances in my instructions to avoid errors. If you want to add another py file to run by cron, you need to add it to the "pick_nam.sh" file* not to the cron. Simply duplicate section 2. lines in the "pick_nam.sh" but without the "#!/bin/bash" part. Then, every time the cron will run "pick_name.sh" it will run all the files you specified inside of it. Make sure to restart cron after changes, it could have saved me a lot of debugging time, use this command:

systemctl restart cron

由于cron在它自己的最小sh环境中执行，下面是我在虚拟环境中运行Python脚本的方法:

* * * * * . ~/.bash_profile; . ~/path/to/venv/bin/activate; python ~/path/to/script.py

(注:如果。~ /。Bash_profile不适合您，那么请尝试一下。~ /。Bashrc或。~ /。配置文件取决于您的服务器如何设置。)

这将加载您的bash shell环境，然后激活您的Python虚拟环境，基本上为您留下与测试脚本相同的设置。

不需要在crontab中定义环境变量，也不需要修改现有脚本。

在venv中添加Python安装路径，但不要激活环境。

* * * * * /HDD1/shritam_kumar/VENOM/venv/bin/python /HDD1/shritam_kumar/Projects/Voelkner-DE/schedule_product_BA.py

就是这么简单。

我很抱歉第n个答案，但我检查了答案，确实有更简单和整洁的答案。

长话短说

在你的cron中使用venv的python二进制文件:

0 3 * * * /home/user/project/env/bin/python /home/user/project/manage.py 

很长的故事

We activate the virtual environment when we want to set the current shell with the python config of that specific virtual environment(that is binaries and modules of that). It is relevant to work with the current shell : execute multiple python commands on the current shell without the need to reference the full python path of the venv. In the frame of a cron or even a bash, which value to activate the environment ? Besides I read in some answers some references to bash rather than sh or still to define a wrapper to call the Python code. But why the hell should we bother with these ?

重复一遍，照做就好:

0 3 * * * /home/user/project/env/bin/python /home/user/project/manage.py 

文件证实:

你不需要特别激活一个环境;激活 只需将虚拟环境的二进制目录前置到您的路径， 这样" python "就会调用虚拟环境的python解释器 您可以运行已安装的脚本，而不必使用它们的全部 路径。但是，在虚拟环境中安装的所有脚本都应该 在不激活它的情况下也可以运行，并使用虚拟机运行 环境的Python自动。