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
api.py
bcrypt.py
brotli.py
brute.py
crawler.py
dbwire.py
deps.py
dialect.py
getch.py
grpcweb.py
gui.py
har.py
hash.py
hashdb.py
jwt.py
keysetdump.py
library.py
nonsql.py
paraminer.py
pivotdumptable.py
progress.py
prove.py
purge.py
safe2bin.py
search.py
sgmllib.py
sqlalchemy.py	Close leaked sqlite3 connections (ResourceWarning on Python 3.13+) (#6181)	2026-11-12 09:46:10 +01:00
sqllint.py
timeout.py
tui.py
versioncheck.py
wafbypass.py
xrange.py