NotificationsYou must be signed in to change notification settings
Fork32k
Star67.3k

gh-133595: Clean up sqlite3.Connection APIs#133605

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

serhiy-storchaka merged 8 commits intopython:mainfromserhiy-storchaka:sqlite3-api-end-deprecation

May 8, 2025

Merged

gh-133595: Clean up sqlite3.Connection APIs#133605

serhiy-storchaka merged 8 commits intopython:mainfromserhiy-storchaka:sqlite3-api-end-deprecation

May 8, 2025

Conversation

Copy link

Member

serhiy-storchaka commentedMay 7, 2025•
edited by github-actionsbot
Loading

All parameters of sqlite3.connect() except "database" are now keyword-only.
The first three parameters of methods create_function() and create_aggregate() are now positional-only.
The first parameter of methods set_authorizer(), set_progress_handler() and set_trace_callback() is now positional-only.

Issue:Finish deprecation period for some sqlite3.Connection APIs #133595

📚 Documentation preview 📚:https://cpython-previews--133605.org.readthedocs.build/

pythongh-133595: Clean up sqlite3.Connection APIs

d60e936

* All parameters of sqlite3.connect() except "database" are now keyword-only.* The first three parameters of methods create_function() and  create_aggregate() are now positional-only.* The first parameter of methods set_authorizer(), set_progress_handler()  and set_trace_callback() is now positional-only.