I don't see any meaningful notes about apps being required to ship migrations beginning with 1.9. I do see deprecation notes about the syncdb signals changing and the syncdb command itself is clearly deprecated. This legacy behavior is handled by sync_apps in the migrate command but there aren't any deprecation warnings raised when it executes. I don't see anything which points to this behavior being deprecated other than this thread.
On Tuesday, March 25, 2014 4:12:42 PM UTC-4, Andrew Godwin wrote: > > So, the functionality whereby you can have apps which do not use > migrations (i.e. that use the old creation backends) is meant to go away in > 1.9 (i.e. the standard three-release deprecation cycle). Most of the > side-effects of this are detailed in > https://docs.djangoproject.com/en/dev/internals/deprecation/#deprecation-removed-in-1-9but > not this one - the fact that setting an empty MIGRATION_MODULE means it > falls back to the old syncdb method (in 1.9, this would just make Django > think that the app had no migrations at all and do nothing, and probably > raise a warning or error). > > The setting itself isn't deprecated, just this undocumented behaviour, so > I haven't put a warning next to it in the docs. > > As for the general TDD problem, we do have the squashing functionality now > so the --update problem is not quite as bad, but I'm not averse to > something like it appearing in 1.8 (1.7 is too frozen now to add it IMO). > > Andrew > > > On Tue, Mar 25, 2014 at 12:01 PM, Shai Berger <[email protected]<javascript:> > > wrote: > >> On Tuesday 25 March 2014 20:36:39 Marc Tamlyn wrote: >> > Do we have an equivalent of south's --update? This would mean you don't >> get >> > many files. We don't want to make it too hard for people to work in a >> > strict TDD fashion. >> > >> +1 >> >> Shai. >> >> -- >> 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] <javascript:>. >> To post to this group, send email to >> [email protected]<javascript:> >> . >> 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/201403252101.52683.shai%40platonix.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/262a32fd-fd5c-495b-a0ba-878372d3f7ea%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
