One option for declaring an app "unmanaged" could be via AppConfig. That's
fairly clean, mirrors the way you can already set a model as unmanaged in
its Meta declaration, and allows for the end user of the app to override by
supplying an AppConfig which will generate migrations (should they, for
some use-case reason, want that).

-- 
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/CAL13Cg9jaODhqc6mrN2xDcURx7SbjL4uWzXugnw%3DeiX8pJfRSg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to