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
Deprecate sqlite3.version and sqlite3.version_info #93370
Comments
But it would be nice to expose the Sqlite 3 version number. What do you think? |
We already do :) |
Not sure what is the process. But I am interested to work on this. |
Sorry for the late reply. Looks like there is already a PR up, however there are probably more deprecations coming up in the 3.12 dev phase :) |
Ok Thank you ! |
Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com> Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com> Co-authored-by: Erlend E. Aasland <erlend.aasland@protonmail.com>
Resolved with #93482 |
The
sqlite3.version
andsqlite3.version_info
attributes have historically created some confusion, as they are sometimes mistaken for the SQLite 3 version number. They used to reflect the pysqlite1 version number, until the external pysqlite package stopped upstreaming changes to the stdlib sqlite3 module2, but today they carry no meaning or practical value3.In order to avoid future frustration, I suggest to deprecate
sqlite3.version
andsqlite3.version_info
in 3.12, and remove them in 3.14.See also discussion on Discourse
Footnotes
The sqlite3 stdlib module was forked off of the external pysqlite module around 2005.↩
Somewhere around 2015, IIRC.↩
sqlite3.version
is set to the value'2.6.0'
, andsqlite3.version_info
is set to the value(2, 6, 0)
.The text was updated successfully, but these errors were encountered: