Piyush satyarthi cb5216564a Close leaked sqlite3 connections (ResourceWarning on Python 3.13+) (#6181) ... Python 3.13+ reports sqlite3 connections that are garbage collected without being closed. The unit tests print a run of "ResourceWarning: unclosed database" lines on Linux/CPython 3.14: - SQLAlchemy.close() only returned its connection to the engine's pool, so the underlying DBAPI connection (e.g. sqlite3 for '-d sqlite://...') stayed open. Dispose the engine on close. - vulnTest() used "with sqlite3.connect(...)", which commits but does not close the connection. Use contextlib.closing(). - test_multibit and test_sqlalchemy never closed what they opened. Co-authored-by: PiyushSatyarthi <244159432+PiyushSatyarthi@users.noreply.github.com>		2026-11-12 09:46:10 +01:00
..
__init__.py
agent.py
bigarray.py
common.py	Implements #6177	2026-11-06 15:31:35 +01:00
compat.py
convert.py	Fixes #6170	2026-11-03 22:04:29 +01:00
data.py
datatype.py	Fix for Ctrl-C hang on Python 3.14 (leaked cache locks)	2026-10-27 13:11:04 +01:00
decorators.py	Fixes CI/CD errors	2026-10-27 13:47:04 +01:00
defaults.py
dicts.py
dump.py
enums.py
exception.py
log.py
option.py	Fixes #6162	2026-10-27 13:29:36 +01:00
optiondict.py
patch.py
profiling.py
readlineng.py
replication.py
revision.py
session.py
settings.py	Fixes #6180	2026-11-10 15:10:16 +01:00
shell.py
subprocessng.py
target.py
testing.py	Close leaked sqlite3 connections (ResourceWarning on Python 3.13+) (#6181)	2026-11-12 09:46:10 +01:00
threads.py
unescaper.py
update.py
wordlist.py