] > > Wouldn't a workaround be to call create_contenttypes() in a RunPython in > your app's migration before inserting the data which depends on the content > types? > > Thanks, but as a workaround you can do almost everything. My post is about proposal of fixing the issue.
BTW: RunPython() is another thing, which can break your migrations, and should not be used (especially not by Django internally), because it relies on the application layer. I discussed about it some time ago. 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/34a6dbc5-0a1c-4c77-be76-8a878a31d336%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
