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 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/21e11bc3-0cb8-489d-85df-a82c5f95fd1e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
