psyucopg2 status

[Gary Doades]

I notice that the documentation is still recommending psycopg1 and not
psycopg2 for PostgreSQL. Psycopg2 has been in release status for quite
a while now. The psycopg site is now firmly recommending psycopg2 and
noting that psycopg1 is effectively obsolete.

It may be better for the documentation,code and particularly for the
upcoming Dango book to make psycopg2 the recommended/default.

[orestis]

In IRC, Jacob KM told me that he is using psycopg2 everywhere now, so I
think that this should be done.

[Russell Keith-Magee]

On 11/7/06, Gary Doades <g...@gpdnet.co.uk> wrote:
>
> I notice that the documentation is still recommending psycopg1 and not
> psycopg2 for PostgreSQL. Psycopg2 has been in release status for quite
> a while now. The psycopg site is now firmly recommending psycopg2 and
> noting that psycopg1 is effectively obsolete.

Historically, the reason for recommending psycopg1 was that the v2
psycopg API had not stabilized; if this has changed, we might want to
look at deprecating the v1 API. I would suggest raising a ticket to
make sure this issue isn't forgotten..

In the interim, psycopg2 support already exists in Django; you can use
the postgresql_psycopg2 backend if you want. Hammering this interface,
identifying any problems that might exist, and reporting on your
results would be one way to expedite the migration process.

Yours,
Russ Magee %-)

[Jacob Kaplan-Moss]

On 11/6/06 6:28 PM, orestis wrote:
> In IRC, Jacob KM told me that he is using psycopg2 everywhere now, so I
> think that this should be done.

Indeed I am; it works just fine.

For now, I'd just suggest using the "postgresql_psycopg2" backend. At some
point, we should probably rename that one "postgresql" and rename the old one
"postgresql_psycopg1" just in case people still need it.

Jacob

[falcon]

I've been using it as well, no problems so far.

[Gary Doades]

Yeah, I've been using it for a couple of months now with no problems. I
also use it on another project via SQLAlchemy.

I only really pointed it out when I saw the beta chapters (chapter 2)
for the book. If it still recommends psycopg1 when it comes out it may
look out of date.

[Cheng Zhang]

Our sites have been using psycopg2 for months without any problem at
all.

－Cheng Zhang
Gentoo/Python/Django Powered
http://www.ifaxian.com
1st Django powered site in Chinese ;-)
http://www.aiyo.cn
Our 2nd Django powered site in Chinese

[David Blewett]

Gary Doades wrote:
> Yeah, I've been using it for a couple of months now with no problems. I
> also use it on another project via SQLAlchemy.
>
> I only really pointed it out when I saw the beta chapters (chapter 2)
> for the book. If it still recommends psycopg1 when it comes out it may
> look out of date.
>

Just wanted to jump on the band wagon. I've been using psycopg2 for ~6
months now and haven't had an issue with it. I think this is a really
valid point. We all know things are out of date as soon as they're
printed, but this would be a real shame to be in the book.

David

[Jacob Kaplan-Moss]

On 11/7/06 2:26 PM, David Blewett wrote:
> Just wanted to jump on the band wagon. I've been using psycopg2 for ~6
> months now and haven't had an issue with it. I think this is a really
> valid point. We all know things are out of date as soon as they're
> printed, but this would be a real shame to be in the book.

Don't worry; we're going to update it.

Jacob