@p @sysrq @MK2boogaloo @istvan >or never start
This part is kinda useful though. That was an issue I had early on; IIRC setting a .py (with a #!/bin/python) +x and just shoving the path to it in cron doesn't actually work for some reason, so I had to spend some time trying to figure out if it was crashing during run or just not running at all.
Or something like that, at any rate. The issue was that it wasn't starting. Maybe cron was logging that error somewhere.