This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients amaury.forgeotdarc, christian.heimes, ghaering, pitrou, python-dev, serhiy.storchaka, vstinner
Date 2013-07-22.06:39:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1374475148.48.0.320655261949.issue18488@psf.upfronthosting.co.za>
In-reply-to
Content
"+1 for PyException_SetContext or similar. The C code should behave like a "finally: x.finalize()"."

If the Python callback failed in _pysqlite_step_callback() or _pysqlite_final_callback(): the exception is printed if sqlite3.enable_callback_tracebacks() has been called, or cleared otherwise.

Only one kind of exception is expected to be passed to be caller (according to sqlite unit tests): AttributeError. The changeset 020dbfdf9517 restores the behaviour of Python 3.3 for best backward compatibility.

If you want better reporting, please open a new issue.

My only concern was just to not call a Python function while an exception is set: I fixed this issue using PyErr_Fetch/PyErr_Restore. So I'm closing the issue.
History
Date User Action Args
2013-07-22 06:39:08vstinnersetrecipients: + vstinner, ghaering, amaury.forgeotdarc, pitrou, christian.heimes, python-dev, serhiy.storchaka
2013-07-22 06:39:08vstinnersetmessageid: <1374475148.48.0.320655261949.issue18488@psf.upfronthosting.co.za>
2013-07-22 06:39:08vstinnerlinkissue18488 messages
2013-07-22 06:39:08vstinnercreate