@corona10 I'm considering addingskip news label here, as this only affects the internal machinery of thesqlite3 module.

as this only affects the internal machinery of the sqlite3 module

@erlend-aasland
I don't think so

Statement instances are no longer weakly referencable

IMHO, At least the statement instance is changed, we can add the news.d about changed caching mechanism.

as this only affects the internal machinery of the sqlite3 module

I don't think so

Right, because of8c888dc, I presume.

Statement instances are no longer weakly referencable

IMHO, At least the statement instance is changed, we can add the news.d about changed caching mechanism.

Even if sqlite3.Statement is not accessible for the user?

$ python3.10>>> import sqlite3>>> sqlite3.StatementTraceback (most recent call last):  File "<stdin>", line 1, in <module>  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/sqlite3/__init__.py", line 37, in __getattr__    raise AttributeError(f"module 'sqlite3' has no attribute '{name}'")AttributeError: module 'sqlite3' has no attribute 'Statement'

@erlend-aasland
Hmm okay, I changed my mind, let's addskip news label :)

Hmm okay, I changed my mind, let's addskip news label :)

:) But notice that itis possible to extract the Statement type using some undocumented tricks:

python3.10Python 3.10.0a7 (v3.10.0a7:53e55290cf, Apr  5 2021, 15:00:06) [Clang 12.0.0 (clang-1200.0.32.29)] on darwinType "help", "copyright", "credits" or "license" for more information.>>> import sqlite3>>> cx = sqlite3.connect(":memory:")>>> stmt = cx("select 1")>>> type(stmt)<class 'sqlite3.Statement'>

True, this is an implementation detail and we don't need to add a NEWS entry.