#16722 closed Bug (fixed)
import psycopg2.Error breaks psycopg2 backend
| Reported by: | Ubercore | Owned by: | anonymous |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Release blocker | Keywords: | psycopg2 Error postgresql import |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The Error class doesn't need to be imported directly. Instead, Database.Error can be used.
Attachments (1)
Change History (7)
by , 13 years ago
| Attachment: | psycopg2_import_error.diff added |
|---|
comment:1 by , 13 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 13 years ago
| milestone: | → 1.4 |
|---|
comment:3 by , 13 years ago
| Keywords: | psycopg2 Error postgresql import added |
|---|
comment:4 by , 13 years ago
by removing the line 25, the django psycopg2 works again.
Sad to see that the SVN is not working tonight :(
comment:5 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
This has been resolved independently by [16710]
Note:
See TracTickets
for help on using tickets.
+ a direct import seems to be impossible at all…