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-44991: Normalise sqlite3 callback naming
#28088
bpo-44991: Normalise sqlite3 callback naming
#28088
Conversation
|
What about This PR turns out to be very small; maybe combine it with the next step if there is one coming? |
Thanks for the heads-up. I'll add it right away.
The next step of normalising is approximately 100 lines added and removed; I think it would clutter things too much. I'm fine with that, but it may be more timeconsuming to review. |
sqlite3 callback suffixessqlite3 callbacks, part 1
sqlite3 callbacks, part 1sqlite3 callback naming, part 1
|
I'll include the other changes; if you think it's too much, we can just revert that commit. I see the diff wasn't as bad as I expected. Only 60-ish lines. |
- all callbacks are now named xxx_callback - normalise callable naming in set_*() functions - normalise context argument naming in callbacks
df3becb
to
0a9d214
Compare
sqlite3 callback naming, part 1sqlite3 callback naming


https://bugs.python.org/issue44991