#36057: Make `test --pdb` pass exception to `pdb.post_mortem()` on Python 3.13
-------------------------------------+-------------------------------------
Reporter: Adam Johnson | Owner: Adam
| Johnson
Type: New feature | Status: assigned
Component: Testing framework | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Adam Johnson):
I haven't checked myself yet, but do you think there is a sensible test to
add to ensure we don't regress in this code?
We don’t seem to have any test coverage of the --pdb option right now, so
it’s not super easy to add. Even if we did, I don’t think we can easily do
it without mocking pdb, which wouldn't cover the change here.
Also, a nitpick, the commit message should "Refs #34900" (same with the
other Python 3.13 related ticket).
Should it? This is to take advantage of a new feature, not to fix
something for the new version. Similarly, my other ticket is a bug that
existed before 3.13, just got better exposed by it.
--
Ticket URL: <https://code.djangoproject.com/ticket/36057#comment:4>
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/0107019429599cad-f7a49fd7-a481-4d2c-9aaa-b34e39820c0f-000000%40eu-central-1.amazonses.com.
