gh-123873: sqlite3.threadsafety aligned with python module capabilities

[rghe]

• Issue: SQLite3 threadsafety property should return 2 for serialized  #123873

[ZeroIntensity]

This is a user-facing bug, we need a news entry.

[rghe]

News added, thank you.

[ZeroIntensity]

I've added the sqlite topic label to get some people who are more familiar with the module on this -- the ASan failures have me a little worried.

[ZeroIntensity]

OK, I don't know what happened with ASan. LGTM.

[erlend-aasland]

Thanks, but I'd prefer if we fixed the root cause. Landing this in main won't help anybody anyway, and backporting to 3.13 is probably out of the question now that we're so close to the final release. (It would have to be 3.13.1 earliest.)

[rghe]

Yes, I understand, but IMHO, even with #118172 fixed, the sqlite module can't share cursors between threads without extensive changes, so returning 3 is still a bug.
Fixing #118172 should allow connection sharing, however, so perhaps a better fix would be returning 2 ?
BTW, I'd like to help, if you think it could be useful.

[python-cla-bot]

The following commit authors need to sign the Contributor License Agreement:

• [email protected]