Hi All, I have a small Django app that uses the sites framework and has a post_save signal on Site that does some bits and bobs when a new site is created. On 1.9.7, when you run migrations for the first time, it correctly triggers the post_save signal. However, after upgrading to 1.10.1, dropping the database, and re-running migrations, the post_save signal I have setup on Site doesn't seem to be triggering. I tried reading the 1.10 release notes and while there was mention of a pre_migrate() and post_migrate() signals, I couldn't make heads or tails on whether that is related.
If this is a deliberate change, can someone please point me to the specifics? If it's a bug, I'd be more than happy to file a bug. Thanks! --Matt -- 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 django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/c386413e-4b56-4673-bfb9-76e5ee851433%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
