I am lost with cron

Troubleshooting
1

hello ,
with dietpi-cron i put in cron.weekly " every sunday at 04:00"
in folder /etc/cron.weekly , i put my script ’ rds1.py’
my script work handling , but no work with cron
my journalctl at 04:00

nov. 10 03:10:01 DietPi CRON[13931]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
nov. 10 03:10:01 DietPi CRON[13932]: (root) CMD (test -e /run/systemd/system || SERVICE_MODE=1 /sbin/e2scrub_all -A -r)
nov. 10 03:10:01 DietPi CRON[13931]: pam_unix(cron:session): session closed for user root
nov. 10 03:17:01 DietPi CRON[13934]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
nov. 10 03:17:01 DietPi CRON[13935]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
nov. 10 03:17:02 DietPi CRON[13934]: pam_unix(cron:session): session closed for user root
nov. 10 03:30:01 DietPi CRON[13962]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
nov. 10 03:30:01 DietPi CRON[13963]: (root) CMD (test -e /run/systemd/system || SERVICE_MODE=1 /usr/lib/arm-linux-gnueabihf/e2fsprogs/e2scrub_all_cron)
nov. 10 03:30:01 DietPi CRON[13962]: pam_unix(cron:session): session closed for user root
nov. 10 04:00:01 DietPi CRON[13969]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
nov. 10 04:00:01 DietPi CRON[13970]: (root) CMD (test -x /usr/sbin/anacron || { cd / && run-parts --report /etc/cron.weekly; })
nov. 10 04:00:01 DietPi CRON[13969]: pam_unix(cron:session): session closed for user root
nov. 10 04:17:01 DietPi CRON[13976]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
nov. 10 04:17:01 DietPi CRON[13977]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
nov. 10 04:17:02 DietPi CRON[13976]: pam_unix(cron:session): session closed for user root
nov. 10 05:17:01 DietPi CRON[14013]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
nov. 10 05:17:01 DietPi CRON[14014]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
nov. 10 05:17:02 DietPi CRON[14013]: pam_unix(cron:session): session closed for user root
nov. 10 06:17:01 DietPi CRON[14050]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
nov. 10 06:17:01 DietPi CRON[14051]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
nov. 10 06:17:02 DietPi CRON[14050]: pam_unix(cron:session): session closed for user root
nov. 10 06:25:01 DietPi CRON[14077]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
nov. 10 06:25:01 DietPi CRON[14078]: (root) CMD (if [ ! -d /run/systemd/system ] && [ -x /usr/libexec/ntpsec/rotate-stats ] ; then /usr/libexec/ntpsec/rotate-stats ; fi)
nov. 10 06:25:01 DietPi CRON[14077]: pam_unix(cron:session): session closed for user root
nov. 10 07:17:01 DietPi CRON[14089]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
nov. 10 07:17:01 DietPi CRON[14090]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
nov. 10 07:17:02 DietPi CRON[14089]: pam_unix(cron:session): session closed for user root

thank for your help

2

In many Linux distributions, like Debian, the cron system (specifically, the run-parts command) expects scripts in directories like /etc/cron.weekly to not have file extensions. This is because run-parts only executes files that follow a strict naming convention, which excludes files with extensions like .sh, .py, etc.

3

ok , thank you , i delete .py