Didn't see 403761 so surely you can close "wontfix" and wait until upstream renames, if it does so.
About all the other requests: From django-developers: http://groups.google.com/group/django-developers/browse_frm/thread/2c373f07be38d451/c10c1e2351747c08?lnk=gst&q=psycopg2&rnum=5&hl=en#c10c1e2351747c08 A discussion about why psycopg1 is still recommended and examples that v1 fails somewhere, as v2 also does (in other places!) From: http://groups-beta.google.com/group/django-users/browse_thread/thread/0a27ec05cce9b353 [..] The only reason to prefer psycopg over psycopg2 is historical - the API for psycopg2 wasn't finalized until quite recently, so we didn't recommend using it. However, the psycopg backend has a few problems with unicode, so I suspect the official line may soon switch to 'use v2' (probably before Django goes v1.0). [..] From the psycopg site (http://initd.org/tracker/psycopg): PsycopgOne -- the original psycopg 1.1.x (now obsoleted by psycopg 2) Anyway, feel free to close as wontfix so people don't complain for another Recommends! Cheers, Marc. On 1/19/07, Raphael Hertzog <[EMAIL PROTECTED]> wrote:
Hello Marc, On Thu, 18 Jan 2007, Marc Fargas wrote: > Package: python-django > Version: 0.95-2 > Severity: normal > > python-psycopg has given some trouble in the past with Django, and it's > often recommended to use python-psycopg2 instead. References ? pointers ? facts ? I never used postgresql with django so I have no idea. > The package could Recommend both and let the user decide. See #403761, people are complaining that we recommend too much already. I'd rather recommend only one python binding per database :-)) If the psycopg2 is the best one, then upstream should rename the db interface postgresql_psycopg2 to postgresql and postgresql to postgresql_psycopg1 ... :-) Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/
