Changes between Initial Version and Version 1 of Ticket #34203, comment 7


Ignore:
Timestamp:
Dec 8, 2022, 10:25:05 AM (19 months ago)
Author:
Paolo Melchiorre

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #34203, comment 7

    initial v1  
    44> I'd ask what are the pros for Django itself?
    55
    6 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.
     6The advantage of dropping support for Psycopg2 2.8 for Django is to avoid that users would open issues related to a version of Psycopg2 that hasn't received new updates for more than 2 years and still supports EOL Python versions (e.g. Python 2.7 and < 3.6)
    77
    88> > Since `Psycopg2 2.8` is **EOL**
    … …  
    1010> 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.
    1111
    12 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.
     12In 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 (2.9, 3.0, 3.1) I find a new 2.8 release highly unlikely.
    1313
    14 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
     14I still don't see any drawbacks for Django to drop support for Psycopg2 2.8 , and I think it could be a gradual way to deprecate Psycopg2 2.9 in 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.
Back to Top