On 08/25/2015 09:23 AM, Marcin Nowak wrote: > On 25 August 2015 at 17:04, Carl Meyer <[email protected] > <mailto:[email protected]>> wrote: > > Hmm, yes, third-party apps are an issue. > > My recollection from the last time you brought this up is that we > decided an AppConfig-level setting to do the equivalent of managed=False > for an entire app would be a reasonable feature request. Since you can > provide your own AppConfig for third-party apps, this would cover that > use case, too. > > > That would be a better than nothing and it's flexible. > > But in the most of my cases I will need to provide app configs for all > apps. This can mean a lot of unnecessary work. > Something like 'disable all' is simplest solution, but naturally limited. > > Maybe there is a solution for both?
Sometimes when you have unusual requirements you have to do a little more work to meet them. To my knowledge, out of the many hundreds of thousands of Django users, you are the first and only one to request a way to turn off migrations entirely. So I don't think there is a very strong need to make that easy, when we can add a more flexible feature that makes it possible. It is not possible to build a framework where _everything_ is easy. We aim for "Simple things should be easy, advanced things should be possible." Carl -- You received this message because you are subscribed to the Google Groups "Django users" 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-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/55DC8971.9030308%40oddbird.net. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
