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 hydroflask
Recipients erlendaasland, hydroflask, pablogsal, vstinner
Date 2022-03-15.19:36:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1647372981.44.0.157590334021.issue47019@roundup.psfhosted.org>
In-reply-to
Content
> All callbacks triggered from external libraries must protect Python C API calls. You may call it offending, but that is the reality; a callback may trigger at any point in time, so we need to make sure the GIL is held before calling any Py API. That is also the case for the destructor.

Sure but I'm suggesting sidestepping and not using the destructor_callback entirely. You can DECREF the callbacks manually in connection_close() after calling sqlite3_close_v2(). Doing this makes sense to me since the destructor may be called under special conditions.
History
Date User Action Args
2022-03-15 19:36:21hydroflasksetrecipients: + hydroflask, vstinner, pablogsal, erlendaasland
2022-03-15 19:36:21hydroflasksetmessageid: <1647372981.44.0.157590334021.issue47019@roundup.psfhosted.org>
2022-03-15 19:36:21hydroflasklinkissue47019 messages
2022-03-15 19:36:21hydroflaskcreate