#36056: Fix ignored exceptions in OutputWrapper.flush()
-------------------------------------+-------------------------------------
Reporter: Adam Johnson | Owner: Adam
Type: | Johnson
Cleanup/optimization | Status: closed
Component: Core (Management | Version: dev
commands) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Adam Johnson):
Thank you for merging.
I would like this to be backported to Django 5.1, although I can see that
it requires a little generosity interpreting
[https://docs.djangoproject.com/en/dev/internals/release-process
/#supported-versions the policy].
On Python 3.13 and pytest, *any* test running a failing management command
triggers this error. On the two projects I’ve seen, that means 10+ copies
of this exception in the output of a full test run. Also, there’s no easy
way to silence the error.
It’s an exception, and we could consider it a “Crashing bug”, given it
crashes part of garbage collection but not the full process.
--
Ticket URL: <https://code.djangoproject.com/ticket/36056#comment:8>
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/010701943b1469c9-91e5f4eb-aa71-4fe3-a141-1cac86033bf4-000000%40eu-central-1.amazonses.com.
