I just read the deprecation timeline and the very brief mention of syncdb command and signals going away doesn't really seem to sufficiently detail the "side-effects" you mention. Anyone who hasn't read your email is going to be unpleasantly surprised. I also don't see any deprecation warnings in the code about this either.
> 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). If I read your statement correctly, you are asking for some one to create a release blocker ticket because taking the position that TDD will be painful in 1.7 and might improve for 1.8 seems wrong. Regards, Michael Manfre On Tue, Mar 25, 2014 at 4:12 PM, Andrew Godwin <[email protected]> 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]> 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]. >> 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/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/CAFwN1upm2g84E6JymtQUgrmBh0vSdfaLU5gNCC-EEopTGx%3D7AQ%40mail.gmail.com<https://groups.google.com/d/msgid/django-developers/CAFwN1upm2g84E6JymtQUgrmBh0vSdfaLU5gNCC-EEopTGx%3D7AQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > 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/CAGdCwBvx4F6FHYd7UGDQz1zi23oTFJN1xPt5L4nM%2Bs03XqFSHQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
