Hi, have you read the 1.9 release notes? Specifically, "When supplying None as a value in MIGRATION_MODULES <https://docs.djangoproject.com/en/1.9/ref/settings/#std:setting-MIGRATION_MODULES>, Django will consider the app an app without migrations." If so, maybe we need a better description of that.
On Wednesday, November 11, 2015 at 3:49:39 PM UTC-5, skyjur wrote: > > Back before django got migrations with south it was possible to do: > > syncdb --all (create all tables old way) > migrate --fake (mark all migrations done) > > This flow was very useful in tests as well as when setting up new projects. > > I'm a bit confused to as to why django took this route and in 1.9 is > making migrations absolutely essential. What are people normally now doing > to avoid running possibly numerous number of migrations every test run or > every time project is deployed from scratch? > > Up until now I was only coming up with workarounds on how to keep my > migrations from running in tests and fresh installs. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/e34a614a-cd0f-43c6-9c01-52f09f24394c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
