Le lundi 23 janvier 2017 20:50:03 UTC+1, Tim Graham a écrit : > > (...) Do you think subclassing and extending the built-in backend is a > common enough use case that it's worth formally deprecating the > postgresql_psycopg2 module rather than simply removing it in Django 2.0? >
I am generally strongly against simply dropping non-internal stuff. In those cases, I would be for a short deprecation period (without pending deprecation) so as at least those who follow the good practice of checking their test suite is deprecation-free on Django n before upgrading to Django n + 1 can have a good experience. Claude -- 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/1d97196b-877f-4d79-8e74-97b1c38d7557%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
