Hi all, I'm moving over to the new migrations, and I've noticed whenever I create a migration involving a custom model field, it imports that field at the top of the migration. The south docs were always quite firm about not doing this sort of thing, in case the code changed in the future. Is this a design decision, i.e. we now expected to make sure imports in our migration files always work in the future? What are the reasons for this? I can imagine this causing issues when refactoring old code for example.
If this is more a question for django-developers, let me know and I'll post it there. Thanks, Greg -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/5636e5d3-53e8-46c5-b26b-ca52be11173c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
