#34203: Drop support for psycopg2 2.8
-------------------------------------+-------------------------------------
Reporter: Paolo Melchiorre | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: postgresql, psycopg | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Paolo Melchiorre):
I agree to deprecate `Psycopg2` in `Django 5.0`, but `Django 4.2 LTS` will
be supported until **April 2026** and I think there will be many `Django
4.2` users who will continue to use `Psycopg2`.
Since `Psycopg2 2.8` is **EOL** , hasn't been updated for **over 2 years**
and barely supports `Python 3.8`, I only see benefits in removing its
support from `Django 4.2` and forcing `Psycopg2` users to at least use the
latest 2.9 series which dropped support for `Python 2.7` / `Python 3` <
3.6 and added support for `Python 3` from 3.6 to 3.11.
What do you think are the cons of removing `Psycopg2 2.8` support from
`Django 4.2` ?
--
Ticket URL: <https://code.djangoproject.com/ticket/34203#comment:5>
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/01070184f1f2f52b-88b80fe4-8a04-4151-b22b-4723eecdcb98-000000%40eu-central-1.amazonses.com.
