Well it was some deleted file's .pyc lying around (models.pyc which was
triggering migrations) :/
Sorry for the noise !
Kind regards,
Olivier
On Fri, Feb 9, 2018 at 10:32 AM, Olivier Dalang <olivier.dal...@gmail.com>
wrote:
> Dear List,
>
> I'm currently trying to deploy a Django 1.8 app and run into a strange
> problem.
>
> My app defines a post-migrate trigger in apps.py :
>
> # apps.py
> class MyAppConfig(AppConfig):
> ...
> def ready(self):
> print('Debug : installing the post-migrate callback')
> post_migrate.connect(my_callback, sender=self)
>
> This works as expected when installed for development (using pip install
> -e /path/to/the/app ) : after migrations, my_callback is correctly called.
>
> But then, when I pip-install the exact same code but without -e : pip
> install/path/to/the/app , the callback isn't called anymore after the
> migrations. The strange thing is that everything else seems to work
> correctly still. Also the debug statement is printed to the console, which
> indicates the post_migrate signal should be connected. It seems all files
> are in the site-package folders...
>
> How come I can get different results depending on whether I install with
> or without -e ?
> Any idea what is happening ?
>
> Thank you very much in advance !!
>
> Olivier
>
>
--
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/CAExk7p3EmjRKTEYoZHXBPi7eNS0dfhVpdAsjed1YfurO%2BLgjpg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
