#35666: Test stack level of deprecation warnings
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Simon
Type: | Charette
Cleanup/optimization | Status: closed
Component: Testing framework | Version: 5.1
Severity: Release blocker | 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
-------------------------------------+-------------------------------------
Changes (by nessita <124304+nessita@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"57307bbc7d88927989cf5b314f16d6e13ade04e6" 57307bbc]:
{{{#!CommitTicketReference repository=""
revision="57307bbc7d88927989cf5b314f16d6e13ade04e6"
Fixed #35666 -- Documented stacklevel usage and testing, and adjusted test
suite accordingly.
Over the years we've had multiple instances of hit and misses when
emitting warnings: either setting the wrong stacklevel or not setting
it at all.
This work adds assertions for the existing warnings that were declaring
the correct stacklevel, but were lacking tests for it.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35666#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 on the web visit
https://groups.google.com/d/msgid/django-updates/010701919971aefc-f4ff0a06-a9cc-4554-80c7-5c9227594ec5-000000%40eu-central-1.amazonses.com.
