Re: Deprecating psycopg 1

2009-12-14 Thread Kevin Teague
On Dec 12, 5:09 pm, Jacob Kaplan-Moss wrote: > > I prefer to think of it like this: > > Django 1.2 ships. Users read the release notes, and notice that > psycopg1 is now deprecated and will be removed. It's still there, and > still supported, so they can upgrade quickly and not have to be stuck

Re: Deprecating psycopg 1

2009-12-12 Thread Tobias McNulty
+1 to removing the psycopg1 backend. I was just wondering if it was ever going to happen earlier today when I was creating example settings files for running the tests, and got tired of typing 'postgresql_psycopg2'. Even getting psycopg1 installed is a small PITA on any modern Linux system. I'll

Re: Deprecating psycopg 1

2009-12-12 Thread Jacob Kaplan-Moss
On Sat, Dec 12, 2009 at 6:36 PM, Jerome Leclanche wrote: > I'm guessing it's the standard way to do things and this may be a bit > offtopic but still, out of curiousity, since the PendingDepWarning is > not visible by default doesn't this actually give the users just the > illusion of more time to

Re: Deprecating psycopg 1

2009-12-12 Thread Jerome Leclanche
I'm guessing it's the standard way to do things and this may be a bit offtopic but still, out of curiousity, since the PendingDepWarning is not visible by default doesn't this actually give the users just the illusion of more time to fix their code? Django releases are, from what I can see, gettin

Re: Deprecating psycopg 1

2009-12-12 Thread Russell Keith-Magee
On Sun, Dec 13, 2009 at 8:13 AM, Jerome Leclanche wrote: > +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. PendingDeprecationWarning lets us introduce the change gradually. * Pe

Re: Deprecating psycopg 1

2009-12-12 Thread Russell Keith-Magee
On Sun, Dec 13, 2009 at 8:02 AM, Jacob Kaplan-Moss 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 k

Re: Deprecating psycopg 1

2009-12-12 Thread Jerome Leclanche
+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 wrote: > On Sat, Dec 12, 2009 at 7:02 PM, Jacob Kaplan-Moss wrote:

Re: Deprecating psycopg 1

2009-12-12 Thread Alex Gaynor
On Sat, Dec 12, 2009 at 7:02 PM, Jacob Kaplan-Moss 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 k

Deprecating psycopg 1

2009-12-12 Thread Jacob Kaplan-Moss
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