Comments on: Creating a Django cron job

By: Mike Kibbel

Mike Kibbel — Sat, 17 Nov 2007 05:13:18 +0000

To solve this problem in a robust way, I’ve extended the method described by Jared Kuolt: http://superjared.com/entry/django-and-crontab-best-friends/. My technique lets you set up the Django environment in your cron job using one line of code without having to type in any long incantations or paths. Check it out and download my reusable script at http://blog.capstrat.com/articles/making-django-environmentally-friendly/

By: Gerald Kaszuba

Gerald Kaszuba — Tue, 29 May 2007 23:12:45 +0000

Heh, fixed the problem almost immediately after asking for help. Isn’t that always the way?

Yes, it’s happened to me countless times!

By: Arthur McLean

Arthur McLean — Tue, 29 May 2007 19:34:14 +0000

Heh, fixed the problem almost immediately after asking for help. Isn’t that always the way? I just added:
sys.path.append(”../”)
That way the import worked fine. Perhaps this will be helpful to someone.

By: Arthur McLean

Arthur McLean — Tue, 29 May 2007 19:26:58 +0000

I’ve tried following the steps outlined here and am getting an error. If I set os.environ['DJANGO_SETTINGS_MODULE'] = ’settings’, I get the error:
ImportError: No module named mytestproject

I’ve also tried with mytestproject.settings and get:
EnvironmentError: Could not import settings ‘mytestproject.settings’ (Is it on sys.path? Does it have syntax errors?): No module named mytestproject.settings

I’m curious if I’m missing something obvious such as where the python script should go? I put my script in the same folder as settings.py. Is that correct?

By: kestrel

kestrel — Mon, 18 Sep 2006 08:48:06 +0000

If a module_name is not a “top-level” module you’ll need to use the following hack:

module = __import__(module_name, globals(), locals(), [''])
getattr(module, function_name)()

By: kestrel

kestrel — Sun, 17 Sep 2006 21:45:23 +0000

You might try this instead of those exec\’s…

module = __import__(module_name)
getattr(module, functio_name)()