Of course RemovedInDjango19Warning is also in 1.7 and a lot of docs reference Django 1.9. I'm not enthusiastic about updating all that.
On Sunday, June 14, 2015 at 1:43:50 AM UTC+2, Loïc Bistuer wrote: > > > > On Jun 13, 2015, at 20:43, Tim Graham <timog...@gmail.com <javascript:>> > wrote: > > > > I don't have a strong opinion either way on semver, but I think it's a > bit late to rebrand 1.9 as 2.0 considering we've release code and docs with > reference to "RemovedInDjango19Warning". Do you have any thoughts on that? > We could plan the change for after the next LTS (2.1 -> 3.0) to correspond > with the cutover to Python 3. > > > Currently we have: > > 1.8: > RemovedInDjango19Warning(DeprecationWarning) - Deprecations from 1.7 > RemovedInDjango20Warning(PendingDeprecationWarning) - Deprecations > from 1.8 > > master: > RemovedInDjango20Warning(DeprecationWarning) - Deprecations from 1.8 > RemovedInDjango21Warning(PendingDeprecationWarning) - Deprecations > from master > > In any case, implementing the new policy will require updating warnings > from master: RemovedInDjango21Warning needs to become either > RemovedInDjango22Warning or RemovedInDjango31Warning with the switch to > SemVer. > > The question is whether it's too invasive to update warnings in a 1.8 > patch release. If we ensure that RemovedInDjango19Warning remains > importable by aliasing it to RemovedInDjango20Warning(DeprecationWarning), > I think it's compatible enough not to delay implementing the scheme by > another two years, especially considering how warnings are normally used. > But if we want to be super cautious we could just leave the code as it is > and document the problem in the 1.8 release notes, after all we are > extending the lifespan of the shims (at least in appearance) which isn't as > problematic as if we were shortening it. > > -- > Loïc > > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/1213b5f4-e7f2-4326-9962-13afa313e554%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
