Hello, On 8 mai 2015, at 17:54, Carl Meyer <c...@oddbird.net> wrote: > > On 05/07/2015 10:20 PM, Tai Lee wrote: >> This sounds good. But will it significantly slow down the rollout of new >> features into Django that require deprecation? > > No, because it would only delay the removal of deprecated features, not > prevent the initial deprecation. The only cost here is the added > maintenance cost of having to keep deprecated code paths around a bit > longer. This cost is non-zero, but in most cases it's quite manageable.
There are some cases where, in order to implement a new feature, you have to wait until a deprecation completes. (In such cases, I have to admit that I try to skip the deprecation path and make a backwards-incompatible change, but that isn’t a good practice.) See my current work on removing database adopters for an example. -- Aymeric. -- 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/023B4E5B-28AF-4EE1-A7C9-154F9AB72D16%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
