-
-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
bpo-43290: Remove pre SQLite 3.5.3 support code from pysqlite_step() #24638
bpo-43290: Remove pre SQLite 3.5.3 support code from pysqlite_step() #24638
Conversation
From the SQLite 3.5.3 changelog: - sqlite3_step() returns SQLITE_MISUSE instead of crashing when called with a NULL parameter.
@berkerpeksag or @serhiy-storchaka, would one of you mind reviewing this? I guess skip news is ok here as well. |
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.
lgtm workaround can be removed ;)
Thank you for reviewing, @corona10 :) |
But I left a comment about this issue, please reply it. Thank you |
I left 11 comments :) |
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.
I haven't read all of the comments (IMO too much discussion for a trivial detail), but looking at the original commit (ghaering/pysqlite@61b3cd9) and the SQLİte changelog, this looks pretty good to me. My only comment is about the superfluous comment.
I'll keep it shorter next time. Most of it was just a note to self about what was going on. I'll remove the comment. |
PTAL, @berkerpeksag |
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.
LGTM, thank you! Will merge once everything is green.
Thank you, @berkerpeksag, I appreciate it. |
From the SQLite 3.5.3 changelog: sqlite3_step() returns SQLITE_MISUSE instead of crashing when called with a NULL parameter. The workaround no longer needed because we no longer support SQLite releases older than 3.7.15.
From the SQLite 3.5.3 changelog:
with a NULL parameter.
https://bugs.python.org/issue43290