#33825: Stop allowing 'django.db.backends.postgresql_psycopg2' in DATABASES
-------------------------------------+-------------------------------------
Reporter: Maxim Danilov | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: db.backend | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* easy: 1 => 0
Comment:
While not documented, the shim still provides backward compatibility for
using that name in the `DATABASES` setting. Whether it could be removed or
should be formally deprecated could be debated. At some point, Django
won't support psycopg2 anymore (#33308 is for adding psycopg3 support)
which will make the alias meaningless.
--
Ticket URL: <https://code.djangoproject.com/ticket/33825#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070181cbd56a2e-c56b2475-dbc1-4606-a20a-bd740ccd5c2b-000000%40eu-central-1.amazonses.com.
