#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):

 Replying to [comment:6 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...
 > I'd ask what are the pros for Django itself?

 The advantage of removing support for Psycopg2 2.8 for Django is to avoid
 opening issues related to a version of Psycopg2 that hasn't received new
 updates for more than 2 years and still supports very old versions of
 Python.

 > > 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.

 In the [https://pypi.org/project/psycopg2/#history history of Psycopg2] I
 have never seen a bugfix release after the release of a subsequent major
 release. Psycopg2 has no official EOL statement, but after more than 2
 years since the last release and 3 major versions released I find a new
 version highly unlikely.

 I still don't see any drawbacks for Django to remove support for Psycopg2
 2.8 , and I think it could be a gradual way to deprecate Psycopg2 2.9
 before Django 5.0, but if you think otherwise, please close this issue,
 because I understand that the priority right now is to complete support
 for Psycop 3.1

-- 
Ticket URL: <https://code.djangoproject.com/ticket/34203#comment:7>
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/01070184f280e0fc-944a7dd4-dc91-4c28-b0a4-dab9b68185bf-000000%40eu-central-1.amazonses.com.

Reply via email to