-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
gh-123873: sqlite3.threadsafety aligned with python module capabilities #124316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
rghe
commented
Sep 22, 2024
•
edited by bedevere-app
bot
Loading
edited by bedevere-app
bot
- Issue: SQLite3 threadsafety property should return 2 for serialized #123873
This is a user-facing bug, we need a news entry. |
News added, thank you. |
Misc/NEWS.d/next/Library/2024-09-23-16-16-06.gh-issue-123873.rzdy2x.rst
Outdated
Show resolved
Hide resolved
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. |
…zdy2x.rst Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, I don't know what happened with ASan. LGTM.
Thanks, but I'd prefer if we fixed the root cause. Landing this in |
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. |
The following commit authors need to sign the Contributor License Agreement: |