On Tue, Sep 9, 2014, Greg Brown <[email protected]> wrote: >Moving over to the new migrations, I noticed that 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?
Hi Greg, You'll get answers to your questions on the django-users email list, <[email protected]> - the web interface is <https://groups.google.com/forum/#!forum/django-users>. The list you've posted to is django-developers, an email list is for the discussion of the development of Django itself. You might also find helpful the #django IRC channel on irc.freenode.net. Daniele -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20140909211106.1593292761%40mail.wservices.ch. For more options, visit https://groups.google.com/d/optout.
