2015-11-19 8:27 GMT+01:00 Claude Paroz :
> To be clear, I don't contest in any way that design choice. I understand
> and approve it.
> I'm just pointing to this unwanted side-effect, wondering if anyone has
> ideas how to circumvent it, as I think it's a legitimate use case.
>
Ah, I misunderstoo
Hello Aymeric,
To be clear, I don't contest in any way that design choice. I understand
and approve it.
I'm just pointing to this unwanted side-effect, wondering if anyone has
ideas how to circumvent it, as I think it's a legitimate use case.
I'm also aware that we have not much control over tes
Hello Claude,
Generally speaking, you cannot safely use a model that isn't defined in an
application that is in INSTALLED_APPS. Django raises a warning when you import
such a model.
This restriction prevents situations where relations between models aren't set
up correctly. There’s a string of
Hello,
I have a Django project with different apps and settings. Let's say
settings A have A in INSTALLED_APPS but not B, and settings B have B in
INSTALLED_APPS but not A. Note also that I cannot have both apps installed,
for some reason.
In that configuration and from Django 1.9, ./manage.py
