#33825: Stop allowing 'django.db.backends.postgresql_psycopg2' in DATABASES
-------------------------------------+-------------------------------------
Reporter: Maxim Danilov | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Normal | Resolution: wontfix
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
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
Yes. Absolutely. And that would be the the deprecation path, if we decided
to go that way.
My point was more, I don't think this is worth the disruption at this
stage, prior to #33308.
(If there's a consensus to remove it then fair enough, otherwise I'd say
let's revisit when adding Psycopg3 support.)
--
Ticket URL: <https://code.djangoproject.com/ticket/33825#comment:4>
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/01070181dd01754f-c5df8e85-4719-4ea3-a2c5-c6835883abd8-000000%40eu-central-1.amazonses.com.
