#22280: "Conflicting models in application" RuntimeError for same model with
different paths
------------------------------+--------------------------------------
Reporter: blueyed | Owner: nobody
Type: Bug | Status: new
Component: Core (Other) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Comment (by aaugustin):
The same model gets imported through two different paths. That used to be
possible, but it's forbidden in Django 1.7.
Django 1.6 and earlier used some rather dark magic to return the same
object instead of a copy, which is what Python does when you import a
module through different paths.
With the information you've provided, I'm not exactly sure why you end up
in this situation, and nothing points to a bug in Django.
Inserting `import sys; print(sys.path)` just before the point where Django
raises an error may help. You could also inspect the content of the app
registry (`from django.apps import apps`) at that point.
--
Ticket URL: <https://code.djangoproject.com/ticket/22280#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.2d325aa53b5880ed0dac0651f93daf57%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
