#22280: "Conflicting models in application" RuntimeError for same model with
different paths
-----------------------------------+------------------------------------
     Reporter:  blueyed            |                    Owner:  nobody
         Type:  Bug                |                   Status:  new
    Component:  Testing framework  |                  Version:  master
     Severity:  Normal             |               Resolution:
     Keywords:                     |             Triage Stage:  Accepted
    Has patch:  0                  |      Needs documentation:  0
  Needs tests:  0                  |  Patch needs improvement:  0
Easy pickings:  0                  |                    UI/UX:  0
-----------------------------------+------------------------------------

Comment (by MalikRumi):

 1. Thanks to all of you for your detailed and ongoing comments which
 helped me understand what is going on.
 2. Blueyed, you are no longer the only one having this issue. I'm not sure
 that's good news.
 3. There are some significant differences in our experiences, however:

 a) I am still pretty new to both Python and Django, so my analytical
 prowess is not as developed as the rest of you. I may be over reporting
 irrelevant information and under reporting the relevant.
 b) I am on a Windows 8.1 machine with Python 2.7 and Django 1.7c1.
 c) I have not run any tests whatsoever. This all started when I ran
 makemigrations for the first time. I got a whole series of errors, and
 shifted to python manage.py shell, where the errors still came up. I was
 working through them one by one until I got to this one:

  {{{ File "G:\Jasmine\Sydney\lib\site-packages\django\apps\registry.py",
 line 201, in register_model    (model_name, app_label,
 app_models[model_name], model))
 RuntimeError: Conflicting 'articles' models in application 'usconst':
 <class 'apps.usconst.models.Articles'> and <class
 'Baillee.apps.usconst.models.Articles'>.}}}

 After reading this ticket, I remembered adding my G: drive to Pythonpath.
 I can't recall now why I did that, but it must have been as a result of an
 earlier error and trying to cover all bases. So I removed that, restarted
 the machine, ran the shell, fully expecting that to resolve my isssue...
 and got the same error.

 I do not have {{{__init.py}}} next to manage.py.
 I installed everything with pip. I did not use .e or any other flags.
 My imports, admin.py. & views.py, are from .models.

 I'm not sure what else you need to know. I look forward to helping
 expedite a resolution.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/22280#comment:21>
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.6dd55bf0584318ed2cea5e17fca7d58a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to