#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 Mariusz Felisiak): Replying to [comment:4 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`. Right 👍 -- Ticket URL: <https://code.djangoproject.com/ticket/33518#comment:5> 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 django-updates+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/063.e202a1b2826c2ca4160e48dc826503bc%40djangoproject.com.