* ui_ux: => 0
* easy: => 1
* stage: Design decision needed => Accepted
Comment:
I'm not sure why this is flagged as DDN. Informative exceptions are good.
--
Ticket URL: <https://code.djangoproject.com/ticket/10494#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* owner: nobody => zefciu
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/10494#comment:4>
* has_patch: 0 => 1
Comment:
Created a patch as a pull request:
https://github.com/django/django/pull/110
--
Ticket URL: <https://code.djangoproject.com/ticket/10494#comment:5>
* stage: Accepted => Ready for checkin
Comment:
Looks good.
--
Ticket URL: <https://code.djangoproject.com/ticket/10494#comment:6>
* status: assigned => closed
* resolution: => fixed
Comment:
In [17917]:
{{{
#!CommitTicketReference repository="" revision="17917"
Fixed #10494 -- Added kwargs to QuerySet.get() error message in the case
no objects were found.
Thanks brondsem for the report, Szymon Pyzalski for the patch and oinopion
for review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/10494#comment:7>
* has_patch: 1 => 0
* resolution: fixed => wontfix
* stage: Ready for checkin => Unreviewed
Comment:
#32522 is a duplicate,
This ticket was fixed in d5b93d3281fe93cbef5de84a52001f64dbd839bd but the
patch was reverted in 266c0bb23e9d64c47ace4d162e582febd5a1e336. I'm not
sure it's worth additional complexity and really helpful for beginners.
We could reopen after a discussion and reaching consensus on
DevelopersMailingList.
--
Ticket URL: <https://code.djangoproject.com/ticket/10494#comment:8>
Comment (by Anders Hovmöller):
It's fairly common that beginners are confused in ways that would be
trivially solved by this improvement. I base this on experience in the
Django Discord.
On a more personal note, this would help me a lot in speeding up debugging
in the rare cases it happens to me in production.
--
Ticket URL: <https://code.djangoproject.com/ticket/10494#comment:9>