id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
33518	Add alias RemovedAfterNextVersionWarning for deprecations after next version	Shai Berger	nobody	"For a very long time, we've had in {{{django.utils.deprecation}}} something like this (from the 3.2 source code):
{{{#!python
class RemovedInDjango40Warning(DeprecationWarning):
    pass


class RemovedInDjango41Warning(PendingDeprecationWarning):
    pass


RemovedInNextVersionWarning = RemovedInDjango40Warning
}}}
Or (current master, towards 4.1):
{{{#!python
class RemovedInNextVersionWarning(DeprecationWarning):
    pass


class RemovedInDjango50Warning(PendingDeprecationWarning):
    pass
}}}

I suggest that we add an alias, {{{RemovedAfterNextVersion}}} for the {{{PendingDeprecationWarning}}} subclass.

The motivation is to make it easier for long-running projects to prepare for future deprecations, with scripts that run tests with special filters on the relevant warnings; currently, such scripts need to be updated for every version. This is especially important for projects which stick to LTS versions, as for them, both warnings need to be treated the same."	Cleanup/optimization	new	Core (Other)	dev	Normal				Unreviewed	0	1	0	0	1	0