The 'django.db.backends.postgresql' alias was added in Django 1.9 along with import shims in the old location: django.db.backends.postgresql_psycopg2 [0]. I'd like to remove the import shims at some point [1] (but keep the two line shim in django/db/utils.py that allows using DATABASES 'ENGINE': 'django.db.backends.postgresql_psycopg2' indefinitely, given the minimal cost). 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?
[0] https://github.com/django/django/commit/bcb4fe0012f8f869348ea83f5a35706f4545c44a [1] https://github.com/django/django/pull/7938 On Sunday, July 26, 2015 at 4:21:14 AM UTC-4, Baptiste Mispelon wrote: > > I finally got around to creating a ticket for this: > https://code.djangoproject.com/ticket/25175 > > On 07/15/2015 03:30 PM, Collin Anderson wrote: > > We definitely should make sure postgresql_psycopg2 still works as > expected. As a data point, Heroku uses "postgres" instead of "postgresql" > in their DATABASE_URL scheme. Maybe we could support all three? :) > > On Wednesday, July 15, 2015 at 9:17:30 AM UTC-4, Baptiste Mispelon wrote: >> >> Hi everyone, >> >> After starting a new project recently and failing three times to type >> the name of the postgres backend correctly, I was wondering if there's >> really any value in keeping around this strange name. >> >> From what I understand, it's a historical artifact from a time when >> there was more than one postgres backend. >> >> >> Could we at least make it an alias of a more simply named "postgresql" >> backend? >> >> >> Thanks, >> Baptiste >> > -- > 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-develop...@googlegroups.com <javascript:>. > To post to this group, send email to django-d...@googlegroups.com > <javascript:>. > 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/3ab4f912-fc25-4859-bd8d-5651e2c68e93%40googlegroups.com?utm_medium=email&utm_source=footer> > https://groups.google.com/d/msgid/django-developers/3ab4f912-fc25-4859-bd8d-5651e2c68e93%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > > > -- 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/416e2f39-8c05-4db7-975f-a5dc16380598%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
