Skip to content
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-42064: Move sqlite3 exceptions to global state, part 2 of 2 #26884

Merged
merged 5 commits into from
Jul 14, 2021

Conversation

erlend-aasland
Copy link
Contributor

@erlend-aasland erlend-aasland commented Jun 23, 2021

https://bugs.python.org/issue42064

Automerge-Triggered-By: GH:encukou

@erlend-aasland
Copy link
Contributor Author

FYI, for check_cursor and pysqlite_check_connection, we cannot rely on the connection context exception pointers (at least not for the early sanity checks), so I'm using the global state in those methods.

@erlend-aasland
Copy link
Contributor Author

(Re-opening to trigger CI again)

@erlend-aasland
Copy link
Contributor Author

cc. @encukou

Modules/_sqlite/module.c Outdated Show resolved Hide resolved
Erlend E. Aasland added 2 commits July 13, 2021 23:10
Copy link
Member

@encukou encukou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks!

@erlend-aasland
Copy link
Contributor Author

Looks good, thanks!

Thanks for reviewing!

@erlend-aasland erlend-aasland deleted the sqlite-move-err/2 branch July 14, 2021 11:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants