Add alias RemovedAfterNextVersionWarning for deprecations after next version

[Shai Berger]

For a very long time, we've had in django.utils.deprecation something like this (from the 3.2 source code):

class RemovedInDjango40Warning(DeprecationWarning):
    pass


class RemovedInDjango41Warning(PendingDeprecationWarning):
    pass


RemovedInNextVersionWarning = RemovedInDjango40Warning

Or (current master, towards 4.1):

class RemovedInNextVersionWarning(DeprecationWarning):
    pass


class RemovedInDjango50Warning(PendingDeprecationWarning):
    pass

I suggest that we add an alias, RemovedAfterNextVersionWarning 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.

[Mariusz Felisiak]

Sounds reasonable, I'm not sure about the name. What do you think about RemovedInVersionAfterNextWarning? Would you like to provide a patch?

[Shai Berger]

Replying to Mariusz Felisiak:

I'm not sure about the name. What do you think about RemovedInVersionAfterNextWarning?

I started with RemovedInNextNextVersionWarning and changed it when I realized that is incorrect for x.0 versions (the pending-deprecation warning is not about the x.2 version, but about the (x+1).0 version). As far as my English goes, that also disqualifies RemovedInVersionAfterNextWarning.

Would you like to provide a patch?

I'm happy to see that someone has already taken it upon themselves. Good luck, Saidblanchette!

[Mariusz Felisiak]

Replying to Shai Berger:

Replying to Mariusz Felisiak:

I'm not sure about the name. What do you think about RemovedInVersionAfterNextWarning?

I started with RemovedInNextNextVersionWarning and changed it when I realized that is incorrect for x.0 versions (the pending-deprecation warning is not about the x.2 version, but about the (x+1).0 version). As far as my English goes, that also disqualifies RemovedInVersionAfterNextWarning.

Right 👍

[Saeed Blanchette]

Replying to Mariusz Felisiak:

Replying to Shai Berger:

Replying to Mariusz Felisiak:

I'm not sure about the name. What do you think about RemovedInVersionAfterNextWarning?

I started with RemovedInNextNextVersionWarning and changed it when I realized that is incorrect for x.0 versions (the pending-deprecation warning is not about the x.2 version, but about the (x+1).0 version). As far as my English goes, that also disqualifies RemovedInVersionAfterNextWarning.

Right 👍

So now we go with the name RemovedAfterNextVersionWarning ?.

---

Thank you Shai Berger 😇.

[Mariusz Felisiak]

So now we go with the name RemovedAfterNextVersionWarning ?.

Yes.

[Shai Berger]

(commit message needs minor tweaking, other than that LGTM)

[Mariusz Felisiak <felisiak.mariusz@…>]

In e559070a:

Fixed #33518 -- Added RemovedAfterNextVersionWarning.