Erlend E. Aasland <erlend.aasl...@innova.no> added the comment:
>From https://sqlite.org/c3ref/close.html: If sqlite3_close_v2() is called with unfinalized prepared statements, unclosed BLOB handlers, and/or unfinished sqlite3_backups, it returns SQLITE_OK regardless, but instead of deallocating the database connection immediately, it marks the database connection as an unusable "zombie" and makes arrangements to automatically deallocate the database connection after all prepared statements are finalized, all BLOB handles are closed, and all backups have finished. The sqlite3_close_v2() interface is intended for use with host languages that are garbage collected, and where the order in which destructors are called is arbitrary. Also: Calling sqlite3_close() or sqlite3_close_v2() with a NULL pointer argument is a harmless no-op. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue26387> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
