bin/chroniker: ImportError: cannot import name setup_environ

[synotna]

Traceback (most recent call last):
  File "/home/esldj/.pyenv/versions/esldj/bin/chroniker", line 8, in <module>
    execfile(__file__)
  File "/home/esldj/.pyenv/versions/esldj/src/django-chroniker/bin/chroniker", line 81, in <module>
    from django.core.management import call_command, setup_environ
ImportError: cannot import name setup_environ

setup_environ was deprecated in django 1.4, https://docs.djangoproject.com/en/dev/releases/1.4/#django-core-management-setup-environ

[synotna]

May I ask, what the purpose of using bin/chroniker is, instead of just using a management command?

[chrisspen]

Thanks for the report. Functionally, there's not much of a difference between bin/chroniker and manage.py cron, other than the bin script tries to be more compact. The bin script is a holdover from the parent chronograph project, but I don't personally use it.

[synotna]

Ah, perhaps change the docs to not imply you should use the bin/chroniker script instead of manage.py cron - I assumed it was for a reason, but went ahead and used manage.py cron anyway

Thanks for the great plugin! Shame it's not better known, I went with django-cron originally as it was easier to "find", and had already started implementing django-celery as an alternative when I came across this!

[chrisspen]

Good suggestion. I'll update that for the next release.

[chrisspen]

This should be fixed in trunk. Please confirm.

[synotna]

thumbs up