#37080: Django's own tests should always treat both Django deprecation warnings
as
errors
--------------------------------------+------------------------------------
Reporter: Mike Edmunds | Owner: (none)
Type: Cleanup/optimization | Status: new
Component: Testing framework | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Mike Edmunds):
Replying to [comment:1 Jacob Walls]:
> > (I think this becomes moot if/when we switch to calendar cycle
releases.)
>
> Can you expand on that part? I'm assuming that part wouldn't change.
The [https://github.com/carltongibson/django-
deps/blob/8693ccc8b949a5cfca1d523f2addd6716464ef8b/draft/0020-annual-
release-cycle.rst#deprecation-policy DEP 20 deprecation policy] doesn't
have the X.0 special cases that result in RemovedInDjango62Warning not
existing, so being omitted from the runtests.py filters. There will always
be two concrete RemovedIn warnings defined…
{{{#!python
# Django 2028.x:
# RemovedInNextVersionWarning (DeprecationWarning):
warnings.simplefilter("error", RemovedInDjango2029Warning)
# RemovedAfterNextVersionWarning (PendingDeprecationWarning):
warnings.simplefilter("error", RemovedInDjango2030Warning)
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/37080#comment:2>
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/0107019de58a4010-58687d12-e0ab-4bd4-b46a-18f1edd4ef64-000000%40eu-central-1.amazonses.com.
