See #103837 (comment) and #103837 (comment):

EAA:

I still think we should consider changing the underlying API so we can emit a resource warning if close failed.

VS:

IMO sqlite3 should be modified to emit a ResourceWarning.

Currently, no ResourceWarning is emitted when a connection is not closed explicitly:

Linked PRs

• gh-105539: Emit ResourceWarning if sqlite3 database is not closed explicitly #108015
• gh-105539: Explict resource management for connection objects in sqlite3 tests #108017
• gh-105539: Fix ResourceWarning from unclosed SQLite connection in ClosedCurTests. #108360
• gh-64662: Fix NEWS entry and remove What's New entry #108565