#35960: Improve most tracebacks with exception chaining
-------------------------------------+-------------------------------------
Reporter: Bartosz Sławecki | Owner: Bartosz
Type: | Sławecki
Cleanup/optimization | Status: closed
Component: Core (Other) | Version: dev
Severity: Normal | Resolution: duplicate
Keywords: exception handling, | Triage Stage:
exception chaining, exceptions, | Unreviewed
raise from |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* component: Uncategorized => Core (Other)
* easy: 1 => 0
* keywords: exception handling, exception chaining, exceptions =>
exception handling, exception chaining, exceptions, raise from
* resolution: => duplicate
* status: assigned => closed
Comment:
Thanks for your interest in Django development.
This was discussed before, so I will mark as a duplicate of #31177.
Although it was decided there that a bulk update was not merited, new code
is always welcome to use `raise from` syntax, and in other cases a case-
by-case decision could be taken if there is a compelling reason (e.g.
silencing unwanted context via `from None`).
--
Ticket URL: <https://code.djangoproject.com/ticket/35960#comment:3>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070193834d81f0-d24929e8-cd91-47cd-ba5e-25cf87e806f0-000000%40eu-central-1.amazonses.com.
