On Wed, Dec 30, 2015 at 11:52 AM, Tim Graham <[email protected]> wrote:
> For that reason, I think we should reconsider making Django's deprecation > warnings loud by default (at least in LTS versions) [1]. Otherwise, users > will pester library authors to fix those warnings and we haven't really > made things easier. > > Instead, the idea would be for library authors to continue using the > deprecated APIs while supporting the LTS in which they are deprecated and > the previous LTS. When the version of Django following the LTS is released, > library authors can then drop support for all Django versions before the > LTS, check their package with the LTS using python -Wall and make the > deprecation warning fixes, then seamlessly add support for the next version > of Django. > > Does that make sense? > This makes sense to me. +1 Regards, Michael Manfre -- GPG Fingerprint: 74DE D158 BAD0 EDF8 keybase.io/manfre -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAGdCwBtcyujD7iLV30o%2BBGUHOc-rvWqgq3TZ3CjDX4CYo4q7xw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
