Maintaining some ability for test applications to have no migrations is very important for Django's own test suite and also other tools such as djangobench. If we're going to maintain some form of code path for that, we should expose it publicly as well.
Marc On 3 June 2015 at 14:29, Markus Holtermann <[email protected]> wrote: > After some discussion with other members of the core team, we think that > we might re-evaluate the point of dropping support for apps without > migrations. But this highly depends on the outcome of what Andrew is going > to achieve in https://code.djangoproject.com/ticket/24481#comment:6 with > regards to the last point. Depending on the actual overhead that comes up > there we'll may or may not enforce migrations for all apps at some point. > > The deprecation timeline marks the removal of support for apps without > migration a part of 1.9. However, since the reason for putting that on the > deprecation timeline was that syncdb used to use the old DDL code, this > argument does not hold anymore. syncdb uses the same DDL code as migrations. > > /Markus > > > On Wednesday, June 3, 2015 at 1:16:37 PM UTC+2, Andriy Sokolovskiy > (coldmind) wrote: >> >> After discussion with Markus Holtermann, we decided that we need to >> deprecate internal syncdb in 1.9 ( >> https://github.com/django/django/blob/7c637a3aaec311269bf863c220bf894eebbe7c7c/django/core/management/commands/migrate.py#L136 >> ) >> The fact that apps without migrations are not supported, which is >> documented for current master, is not fully right, because migrate command >> is still calling syncdb inside. >> I think it is time to drop support of apps without migrations internally, >> so in 2.0, after users will be warned in 1.9, we can remove syncdb and >> create >> schema only from migrations and require all installed apps with models to >> have migrations. >> > -- > 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/7d2fd535-40b3-4c83-845b-72d248096587%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/7d2fd535-40b3-4c83-845b-72d248096587%40googlegroups.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 (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/CAMwjO1EwpYDEqVF%2BtKxvtt2xWHzYUWpmoCbx3LwppYnUHCReTw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
