Recursive import with Django's comments and South breaks syncdb about django-reversion HOT 9 CLOSED

This issue was copied over from the old Google Code site.

http://code.google.com/p/django-reversion/issues/detail?id=67

from django-reversion.

As outlined on the old comment thread, this is an unusual conflict between several different Django applications.

The blame appears to lie mostly with the django.contrib.comments app.

from django-reversion.

A possible solution would be to remove the post_syncdb hook and refactor it into an admin command. Any thoughts, people?

from django-reversion.

I'm +1 on moving the post_syncdb to a management command: something like ./manage.py create_initial_reversions <path.to.model>, where if <path.to.model> wasn't provided it would attempt to run for all models registered with reversion.

from django-reversion.

just did that http://pastebin.com/JJMC0xLz
doesn't run on all models yet just on the apps/models specified

from django-reversion.

Looks reasonable.

If you can make it work on all registered models if run without any arguments, I'll have a go at integrating it.

Even better, build it in a fork and I'll do a pull.

from django-reversion.

done

from django-reversion.

I've pulled in your work. Many thanks! It works like a dream.

I ended up renaming the management command, hope you don't mind!

from django-reversion.

thx for pulling it!

no i don't mind but i must admit that i do like the idea of having a prefix for management commands so you don't end up with a mess if you do "./manage help". that way you could idenfitfy easily where that command comes from or find quicker what you're looking for since it's somewhat sorted.

from django-reversion.