#21619: SingleObjectMixin raises ObjectDoesNotExist, rather than a more specific
subclass
-------------------------------------+-------------------------------------
Reporter: Keryn Knight | Owner: pjrharley
<django@…> | Status: closed
Type: | Version: master
Cleanup/optimization | Resolution: fixed
Component: Generic views | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by Baptiste Mispelon <bmispelon@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"cdd6617da679e19059907979b03c4ef7b15691e6"]:
{{{
#!CommitTicketReference repository=""
revision="cdd6617da679e19059907979b03c4ef7b15691e6"
Fixed #21619 -- Made SingleObjectMixin.get_object catch a more precise
exception.
Thanks to Keryn Knight for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/21619#comment:6>
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/095.c4dbe8f42d3f50847a331835b37f8b81%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
