Re: [psycopg] #183: Asynchronous exceptions
"psycopg" <fog-NGVKUo/i/[email protected]>
| Newsgroups | gmane.comp.python.db.psycopg.devel |
|---|---|
| Message-ID | <[email protected]> |
#183: Asynchronous exceptions
-----------------------+----------------------------------------------------
Reporter: Clodoaldo | Owner: fog
Type: defect | Status: new
Priority: normal | Milestone: PSYCOPG 2.0.7
Component: psycopg2 | Version: 2.0.5
Severity: normal | Resolution:
Keywords: |
-----------------------+----------------------------------------------------
Comment (by jamesh):
The described behaviour sounds like an exception is being raised with
PyErr_SetString() but NULL is not being returned.
At some later point, Python notices the exception, causing it to appear to
come from some other location. All it would take is one buggy error
handling block somewhere to trigger this.
The exceptions aren't being delivered asynchronously, but instead being
raised improperly.
--
Ticket URL: <http://initd.org/tracker/psycopg/ticket/183#comment:1>
psycopg <http://initd.org/>
psycopg