+1 from me too on the timeline, but why the PendingDeprecationWarning? I don't see the point, there isnt exactly a limit to how long something can be deprecated.
J. Leclanche / Adys On Sat, Dec 12, 2009 at 6:04 PM, Alex Gaynor <alex.gay...@gmail.com> wrote: > On Sat, Dec 12, 2009 at 7:02 PM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: >> Hi folks -- >> >> I'd like to start the process of deprecating and removing support for >> psycopg 1. Why? >> >> * psycopg 2 is better in every way. >> * psycopg 1 hasn't been updated since October 2005; it's basically a dead >> end. >> * I don't know anyone using it in production. >> * For the couple-three people who *are*, it's now possible (and >> reasonably easy) to maintain an external backend. >> >> I'm proposing the following very predictable timeline: >> >> Django 1.2 >> Use of the "postgresql" backend raises a PendingDeprecationWarning. >> >> Django 1.3 >> Use of the "postgresql" backend raises a DeprecationWarning. >> >> Django 1.4 >> Remove the "postgresql" backend from Django (and put it on >> bitbucket/github?) >> >> Any objections? >> >> [I'm deliberately not discussing anything regarding the renaming of >> the "postgresql_psycopg2" backend. I have a bigger proposal I'd like >> to make around that, but that's gonna have to wait for 1.3.] >> >> Jacob >> >> -- >> >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To post to this group, send email to django-develop...@googlegroups.com. >> To unsubscribe from this group, send email to >> django-developers+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/django-developers?hl=en. >> >> >> > > +1. psycopg1 is already missing quite a few features from psycopg2 > (autocommit, GIS, etc.). > > Alex > > -- > "I disapprove of what you say, but I will defend to the death your > right to say it." -- Voltaire > "The people's good is the highest law." -- Cicero > "Code can always be simpler than you think, but never as simple as you > want" -- Me > > -- > > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-develop...@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
