I think if I were doing this, I would go the route of using MIGRATION_MODULES and copying the reusable app's migrations into it, then adding my own migrations. Yes, this would require copying any new migrations from an updated version of the app, but I am a bit nervous about adding more complexity in Django to support other ways of doing it. Too often, these edge case scenarios aren't considered when adding new features or making changes and they inadvertently get broken in some edge cases. Modifying models in other apps using contribute_to_class() isn't a blessed solution as far as I know, so adding features to support it doesn't feel right to me unless we make that blessing first.
On Tuesday, September 1, 2015 at 4:09:44 AM UTC-4, Emmanuelle Delescolle wrote: > > Quote from Russ Magee's Twitter > >> Django 1.9 is coming - do you have something on your wishlist? DSF Fellow >> Tim Graham has an offer for you: groups.google.com/d/msgid/django… > > > Well, actually, I'd really like this for 1.9 ;-) > > Has anyone +1's for this or is it more like -1's ? > > >> Sample project is available at >> https://bitbucket.org/emma_nuelle/migrate_othe_app_sample. Django branch >> is at https://github.com/nanuxbe/django/tree/migrate_other_app <-- >> current test suite seems to pass fine (at least on my computer) just >> missing new tests if actual PR has to be made >> > > > Cheers, > Emma > -- 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/7a8958ca-9021-4933-9fca-4b41e8110411%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
