#27360: Make it easier to track down the offending models for AlreadyRegistered
exceptions
--------------------------------------+------------------------------------
     Reporter:  Ed Morley             |                    Owner:  nobody
         Type:  Cleanup/optimization  |                   Status:  new
    Component:  contrib.admin         |                  Version:  1.8
     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 Quentin Fulsher):

 It might be a good idea to add the model's `__module__` field in front of
 the model name. Suppose for example I defined the model `UserModel` in
 `app1.models`. This would turn the resulting exception's message to
 `AlreadyRegistered: The model app1.models.Site is already registered`.
 Does this sound like a good addition?

--
Ticket URL: <https://code.djangoproject.com/ticket/27360#comment:2>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.d7e3b8053d8002e75663930296d1d540%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to