Core could stay at 2.4.5 and contrib.postgresql could require a newer version :)
On Saturday, February 14, 2015 at 9:53:43 PM UTC+1, Marc Tamlyn wrote: > > Hi all, > > Related ticket - https://code.djangoproject.com/ticket/24335 > > Django 1.8 will necessarily be the first version with a true minimum > requirement on psycopg2 version. Historically we have never documented a > required version. > > - The new UUIDField requires at least 2.0.9 > - Some code which is currently contained in the backend, not in > contrib.postgres, but I think only relates to arrays of > (Generic)IPAddressFields requires 2.4.5. As yet I have not tried moving > this compat code so it only runs if contrib.postgres installed. > - Range fields (in contrib.postgres) require 2.5 > - There may be other things I'm not responsible for I don't know about, > with different version requirements. > > Release history for psycopg2: > - 2.0.9 is extremely old (date unknown) > - 2.4.5 was released in March 2012 > - 2.5 was released in April 2013 > - 2.6 was released this month (Feb 2015) > > According to Claude, some distros have a python-psycopg2 package which is > still on 2.4.5 (or maybe older?). > > We have several options: > - Ensure as much as possible works with old versions of psycopg2 by > shuffling code around and/or using conditional imports. > - Making sure everything *outside contrib* doesn't require newer psycopg2 > that 2.0.9, and making contrib.postgres require 2.5. This may not be > possible, but I think it should be. > - Change nothing but docs, so outside contrib requires 2.4.5, > contrib.postgres requires 2.5. > - Just document that Django 1.8+ needs psycopg2 2.5 (pip install it...) > > The latter would be my preferred option, but then I've never understood > the argument for distro packages instead of pip. In any case, I feel that > any distro not supporting a two year old version of psycopg2 is unlikely to > be distributing a brand new version of Django. > > As far as I know we have no official policy on dependencies like this (we > don't have many). > > Marc > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/dbde195e-39e8-438c-a30d-f95911e1b5ee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
