#22280: "Conflicting models in application" RuntimeError for same model with
different paths
------------------------------+--------------------------------------
Reporter: blueyed | Owner: nobody
Type: Bug | Status: closed
Component: Core (Other) | Version: master
Severity: Normal | Resolution: needsinfo
Keywords: app-loading | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Comment (by blueyed):
Yes, both `project` and `project/project` are in sys.path:
`sys.path` looks as follows when the exception gets raised (and also
before the relative imports):
'/project'
'/project/virtualenv/src/autocomplete-light'
'/project/project'
'/project/virtualenv/src/django-grappelli'
...
But also with only `project/project` on sys.path (depending on the package
/ __init__.py layout), the problem persists: it's just different then how
the conflicting model is named.
> I suspect __fake__.Person is just a misdirection caused by the
migrations framework.
Does this mean, it should not show up as "__fake__." here?
--
Ticket URL: <https://code.djangoproject.com/ticket/22280#comment:10>
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.6748e4b2a4b8d0aec8fe399525a0b20d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
