#33518: Add alias RemovedAfterNextVersionWarning for deprecations after next
version
-------------------------------------+-------------------------------------
Reporter: Shai Berger | Owner:
Type: | Saidblanchette
Cleanup/optimization | Status: assigned
Component: Core (Other) | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Shai Berger):
Replying to [comment:2 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!
--
Ticket URL: <https://code.djangoproject.com/ticket/33518#comment:4>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/063.5967a3749a609fdd0cd38f18bb7a2fe8%40djangoproject.com.
