|south and django 1.3.1||Jan Vilhuber||12/23/11 3:54 PM|
I manage some django tables with south as well, and was just experimenting with 1.3.1 which I hope to switch to very soon.
As with most custom types, I needed to add:
from south.modelsinspector import add_introspection_rules
Now when I start my app, I get:
If I remove the instrospection rule and import, it starts fine, but then of course manage.py schemamigration complains.
What's the right way to do this? Is there a way I can detect if this is being included as part of a schememigration, i.e. a conditional include?
|Re: south and django 1.3.1||Andrew Godwin||12/24/11 9:51 AM|
I'm not sure why that's failing - looks weirldy like a circular import issue.
Is it just the import that does this, or the call as well?
Jan Vilhuber <jan.vi...@gmail.com> wrote:
|Re: south and django 1.3.1||Jeremy Dunck||12/24/11 10:31 AM|
It looks like you've modified Django auth to depend on south? Don't do that; nearly everything depends eventually on auth, and that will cause you lots of pain.