-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
[sqlite3] cleanup callbacks (GIL handling, naming, ...) #89154
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
Comments
Quoting msg400205 by Petr in bpo-42064:
|
I'd like to propose further enhancements:
If you agree, I'll create separate PR's for those; one for each refactor. I think it will enhance readability a lot. |
The general policy is to only improve style for code you touch for some other reasons. You're changing lots of the callback code in bpo-42064, so I reckon making things more readable is fine. |
Obviously, this case could be code churn(we don't accept normally), but if other core-dev agree with the changes. I am fine. |
We'll do the changes Petr proposed first, and then I'll see how invasive the other changes will be. If the diffs end up being concise, I'll put them up for review :) |
The remaining function_pinboard_* renames are part of PR-27940. |
sqlite3
callbacks #27934sqlite3
callback naming #28088sqlite3
function and collation callback naming #28209Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: