Tim recently did a fabulous job of removing deprecated code for the future 1.9 on master. Thanks for that.
However, one thing he removed was support for apps without migrations. https://github.com/django/django/commit/7e8cf74dc74539f40f4cea53c1e8bba82791fcb6 Considering that we have to keep internal support for Django's own test suite anyway, I wonder if we should remove that support at all for "normal" projects. I think one of Andrew's motivation was not to have to keep two schema editing code bases. But now that the old syncdb also uses the new schema editor, I think that this argument doesn't stand. So what about keeping support for apps without migrations in the longer term. Of course, the fact that those apps cannot depend on migrated apps limits its use, but I think that for quick prototyping and initial developement, migrations could be more of a hindrance. Would you see major drawbacks with keeping this support? Opinions welcome. Claude -- www.2xlibre.net -- 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 [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/1421617394.5741.4.camel%40doulos. For more options, visit https://groups.google.com/d/optout.
