Opened 9 years ago

Closed 9 years ago

#24036 closed New feature (fixed)

Ignore deprecation warnings in tests depending on the Django version

Reported by: Aymeric Augustin Owned by: nobody
Component: Testing framework Version: dev
Severity: Normal Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


We used to replace all PendingDeprecationWarning with DeprecationWarning after each release. We introduced RemovedInDjangoXYWarning to solve this problem.

We're still replacing IgnorePendingDeprecationWarningsMixin with IgnoreDeprecationWarningsMixin. We should introduce a similar solution.

Change History (5)

comment:1 Changed 9 years ago by Claude Paroz

Triage Stage: UnreviewedAccepted

I'll try to have a look at it.

comment:2 Changed 9 years ago by Claude Paroz

Has patch: set

See, does that look like what you had in mind?

comment:3 Changed 9 years ago by Tim Graham

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.

comment:4 Changed 9 years ago by Tim Graham

Triage Stage: AcceptedReady for checkin

comment:5 Changed 9 years ago by Claude Paroz

Resolution: fixed
Status: newclosed
commit 51890ce8898f821d28f2f6fb6071c936e9bd88f0
Author: Claude Paroz <>
Date:   Sun Dec 21 21:19:05 2014 +0100

    Applied ignore_warnings to Django tests

commit 66f9a74b4514bd259976ce8ee3a4e78288358a5f
Author: Claude Paroz <>
Date:   Sun Dec 21 21:13:06 2014 +0100

    Added ignore_warnings decorator
    And removed Ignore*DeprecationWarningsMixin, now obsolete.
    Thanks Berker Peksag and Tim Graham for the review.
Note: See TracTickets for help on using tickets.
Back to Top