Django

Code

Ticket #3076 (closed: duplicate)

Opened 2 years ago

Last modified 2 years ago

Docs should recommend psycopg2, not recommend against it

Reported by: joaoma@gmail.com Assigned to: jacob
Milestone: Component: Documentation
Version: Keywords: psycopg2
Cc: Triage Stage: Accepted
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

The Django docs currently state that psycopg1 is recommended because 2.0 "is still in beta". Psycopg2 has been stable for a long time, so, the docs are really obsolete. I'm marking this as normal because psycopg2 is *MUCH* better, specially for handling international characters.

Attachments

Change History

01/21/07 23:36:00 changed by Simon G. <dev@simon.net.nz>

  • keywords set to psychopg2.
  • stage changed from Unreviewed to Accepted.

There *used to be* a number of issues with psychopg2 not working (e.g. http://groups.google.com/group/django-developers/browse_thread/thread/4575a3fe0d78e2e4/7ee0ed2140a947ef?lnk=gst&q=psycopg2&rnum=2#7ee0ed2140a947ef)

Can anyone confirm whether psychopg2 works properly or not?

01/24/07 19:10:03 changed by Gary Wilson <gary.wilson@gmail.com>

  • keywords changed from psychopg2 to psycopg2.
  • status changed from new to closed.
  • resolution set to duplicate.

marking this a dup of #3364 since it has a patch.

02/08/07 16:10:39 changed by lbolognini@gmail.com

Always (it's been 5 months) been running on psycopg2 and never had a problem. But then i must say i'm not running anything in production yet. My experience is with WinXP, Python 2.4, Psycopg2 and Django svn.

Add/Change #3076 (Docs should recommend psycopg2, not recommend against it)




Change Properties
Action