#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 Mariusz Felisiak):
> What do you think are the cons of removing `Psycopg2 2.8` support from
`Django 4.2` ?
Normally we don't bump minimum supported versions of 3rd party packages
when it's not necessary (e.g. they're not compatible with the current
Django version, or they require some workarounds in Django). I'd ask what
are the pros for Django itself?
> Since `Psycopg2 2.8` is **EOL**
What is the source of this information? There are commits in the
[https://github.com/psycopg/psycopg2/commits/maint_2_8 maint_2_8] branch
after the 2.8.6 release, so as far as I'm aware, we cannot assume that
`2.8.7` will not be released in the future.
--
Ticket URL: <https://code.djangoproject.com/ticket/34203#comment:6>
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/01070184f222580e-b91eba1d-b334-40bf-8db5-c21aff5b800b-000000%40eu-central-1.amazonses.com.
