#24036: Ignore deprecation warnings in tests depending on the Django version
-----------------------------------+------------------------------------
Reporter: aaugustin | Owner: nobody
Type: New feature | Status: new
Component: Testing framework | Version: master
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 timgraham):
On the one hand, I like that the current scheme is very explicit in that
we put only the code which raises the warning in a `catch_warnings()`
block. On the other hand it's very verbose, error-prone, and sometimes
confusing to new contributors. The decorator syntax seems very nice and it
seems great to standardize the method used on classes and methods so +1
from me if there are no other objections.
--
Ticket URL: <https://code.djangoproject.com/ticket/24036#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.736ceb62c1cdc50cb82683dfc999d3d0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
