#24851: Regression in reverse one-to-one field in list_display
---------------------------------+------------------------------------
Reporter: jerivas | Owner: nobody
Type: Bug | Status: new
Component: contrib.admin | Version: 1.8
Severity: Release blocker | 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 jerivas):
Whoops, you're right, I was only using `list_display` in 1.6. Sorry about
that.
However, wouldn't it be appropriate to support reverse one-to-one
relations in `fields`? I see three possible scenarios:
- Reverse one-to-one relations fully supported in `fields`.
- Supported only when they appear in `readonly_fields`.
- Unsupported, but they raise a more useful exception and is explained in
the docs. The current exception says the one-to-one field is unknown to
the model, which is confusing and gives the impression the user has made a
typo in `fields`. IMO `ImproperlyConfigured` would be better.
If you think any of the above have the potential of flying as a feature
request, I can open a new ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/24851#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/065.9c2883e14db87eaa3c9235438e65cda8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
