On Sunday, May 31, 2015 at 1:47:32 AM UTC+2, Tim Graham wrote: > > They were dropped as part of the removal of the old code that supported > syncing apps without migrations. >
But you removed a feature, not just old code. In v1.8 (1.7 maybe?) this feature was broken (issue #24876) and it was completely removed in master (issue #24481). This is not good. > > By the way, I suspect this could be implemented as a third-party app if > there is opposition to including it in Django itself. > I know I can reimplement it myself, but core feature should be nearest to core source code, because it highly depends on internals. This can be provided as a contrib app, for example. Why contrib.gis is supported for years? This app is used rarely. In contrast to gis - we generate/create SQLs every day. I don't know what you're doing with Django, but latests changes looks fearfull.. :( /BR Marcin -- 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/6ee9daaa-a619-4507-ae7f-0ed72d41a867%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
