1. If the subject added the sentence #!/usr/local/bin/python2.7 to xxx.py, then your crontab scheduled task definition only needs to be:

0 0 * * * /x/xxx.py

Because the first line of the script specifies the interpreter and it is already an executable script (file), there is no need for python2.7 to execute the command.

2. If you don’t write the first line to specify the environment variable, I usually write it like this because there are multiple versions in my environment

0 0 * * * /usr/local/bin/python2.7 /x/xxx.py

To specify the path for python execution, it is recommended that you write like this

3. Why does crontab need to specify the python path?

The official document explains this:

Environment variables have been automatically set, such as the current SHELL, SHELL=/bin/bash, and the HOME directory of the crontab owner is read from the /etc/passwd file. In addition to the default environment variables, other environment variables need to be set by the user. In order to find python2.7, it is necessary to set PATH=/user/local/bin

4. About debugging

Generally, if cron is not executed, an error email will be sent, usually under /var/mail by default

After several tests, we came to the conclusion that there is a problem with the get_dongqiudi.py script, so the new problem is,

This script can be executed manually, but why does it not take effect in crontab?

---

I just rebuilt a mkfile.py file and put it in crontab to execute it regularly every minute. It can be executed normally

But once the code is changed to this, it cannot be run in crontab and can only be run manually

The following code

#!/usr/local/bin/python3 import time file_name = '文章id'+ str(time.time()) f = open('/home/'+file_name,'w') f.close()