Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#16722 closed Bug (fixed)

import psycopg2.Error breaks psycopg2 backend

Reported by: Ubercore Owned by: anonymous
Component: Database layer (models, ORM) Version: master
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)

psycopg2_import_error.diff (939 bytes) - added by Ubercore 5 years ago.

Download all attachments as: .zip

Change History (7)

Changed 5 years ago by Ubercore

Attachment: psycopg2_import_error.diff added

comment:1 Changed 5 years ago by Florian Apolloner

Owner: changed from nobody to anonymous
Status: newassigned

+ a direct import seems to be impossible at all…

comment:2 Changed 5 years ago by Florian Apolloner

milestone: 1.4

comment:3 Changed 5 years ago by Ubercore

Keywords: psycopg2 Error postgresql import added

comment:4 Changed 5 years ago by anonymous

by removing the line 25, the django psycopg2 works again.
Sad to see that the SVN is not working tonight :(

comment:5 Changed 5 years ago by Russell Keith-Magee

Resolution: fixed
Status: assignedclosed

This has been resolved independently by [16710]

comment:6 Changed 5 years ago by Jacob

milestone: 1.4

Milestone 1.4 deleted

Note: See TracTickets for help on using tickets.
Back to Top