2013/8/13 Chris Wilson <ch...@aptivate.org> > It certainly seems that people are eager to rip things out the very second > that the deprecation waiting period expires and they are "allowed" to.
If someone introduced a deprecation with a PendingDeprecationWarning, and someone else later advanced all PendingDeprecationWarnings to DeprecationWarnings, that deprecation would start immediately with a DeprecationWarning. To avoid this problem, every time we fork a stable branch from master, we must: 1) remove all code that's under DeprecationWarning, 2) bump PendingDeprecationWarning to DeprecationWarning. And then we're in a position where it's safe to introduce new deprecations. You may be under the impression that we're rushing to remove deprecated code, but that isn't the whole story. It's necessary to avoid accidentally accelerated deprecations. -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" 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. For more options, visit https://groups.google.com/groups/opt_out.
