[issue44073] [sqlite3] drop statement in_use field in favour of sqlite3_stmt_busy()

Erlend E. Aasland added the comment: See also bpo-44958 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue44073] [sqlite3] drop statement in_use field in favour of sqlite3_stmt_busy()

Change by Erlend E. Aasland : -- keywords: +patch pull_requests: +24636 stage: -> patch review pull_request: https://github.com/python/cpython/pull/25984 ___ Python tracker __

[issue44073] [sqlite3] drop statement in_use field in favour of sqlite3_stmt_busy()

Erlend E. Aasland added the comment: $ git diff --stat Modules/_sqlite/connection.c | 1 - Modules/_sqlite/cursor.c | 5 + Modules/_sqlite/statement.c | 14 +- Modules/_sqlite/statement.h | 2 -- 4 files changed, 2 insertions(+), 20 deletions(-) -- __

[issue44073] [sqlite3] drop statement in_use field in favour of sqlite3_stmt_busy()

New submission from Erlend E. Aasland : sqlite3_stmt_busy() has been around since SQLite 3.7.10. I suggest to drop the in_use field of pysqlite_Statement in favour of sqlite3_stmt_busy(); we do not need to duplicate functionality already present in SQLite. There was a bugfix for sqlite3_stmt_