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 benjamin.peterson
Recipients benjamin.peterson, berker.peksag, gescheit, ghaering
Date 2019-06-24.18:38:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1561401530.08.0.0929300676971.issue37347@roundup.psfhosted.org>
In-reply-to
Content
The _sqlite3 module clearly is not free of bugs in this area. Binding the Python function to the exact lifetime of the sqlite function seems less likely to be buggy than replicating sqlite's function reference management independently. sqlite3_create_function_v2 was added in 2010; I think we can depend on it. Also, won't the callback pretty much be Py_DECREF(something)?
History
Date User Action Args
2019-06-24 18:38:50benjamin.petersonsetrecipients: + benjamin.peterson, ghaering, berker.peksag, gescheit
2019-06-24 18:38:50benjamin.petersonsetmessageid: <1561401530.08.0.0929300676971.issue37347@roundup.psfhosted.org>
2019-06-24 18:38:50benjamin.petersonlinkissue37347 messages
2019-06-24 18:38:49benjamin.petersoncreate