I remembered a thing from Michaels talk at #DUTH. Let me present a use case for subclassing a backend:
https://github.com/opbeat/django-postgres-readonly/blob/master/django_postgres_readonly/base.py I think if we end up favouring immediate deprecation, we could proactively find and inform backend maintainers that would be affected. Their users might not be so appreciative though. I think Claude's position is a good one. A short deprecation period at a minimum. For my own interest I just did a quick search on PyPI for `django postgres` and found the following (having various levels of django version support): https://github.com/2degrees/django-postgres-delete-cascade/blob/master/django_postgres_delete_cascade/base.py https://github.com/kennethreitz/django-postgrespool/blob/master/django_postgrespool/base.py https://github.com/jdelic/django-postgresql-setrole/blob/master/postgresql_setrole/__init__.py (this one imports from the new location!) -- 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/1755d125-ee5e-402f-bbd2-c6edb4c720c6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
