[issue43505] [sqlite3] Explicitly initialise and shut down sqlite3

Erlend Egeberg Aasland added the comment: > Making SQLITE_OMIT_AUTOINIT the default behavior would pretty much break > every application that use SQLite [...] Yeah, I know, _but_ if some user decides use a SQLite library compiled with SQLITE_OMIT_AUTOINIT (because it is mentioned in the "Rec

[issue43505] [sqlite3] Explicitly initialise and shut down sqlite3

Change by Berker Peksag : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue43505] [sqlite3] Explicitly initialise and shut down sqlite3

Berker Peksag added the comment: New changeset def919342facf7f53a3a5f0e9f4b1889d323956d by Erlend Egeberg Aasland in branch 'master': bpo-43505: Explicitly initialize and shutdown sqlite3 (GH-25404) https://github.com/python/cpython/commit/def919342facf7f53a3a5f0e9f4b1889d323956d --

[issue43505] [sqlite3] Explicitly initialise and shut down sqlite3

Berker Peksag added the comment: Making SQLITE_OMIT_AUTOINIT the default behavior would pretty much break every application that use SQLite, but since the PR is small enough and uses the interface in the correct way, I don't see a strong reason to reject it. -- _

[issue43505] [sqlite3] Explicitly initialise and shut down sqlite3

Change by Erlend Egeberg Aasland : -- keywords: +patch pull_requests: +24137 stage: -> patch review pull_request: https://github.com/python/cpython/pull/25404 ___ Python tracker _

[issue43505] [sqlite3] Explicitly initialise and shut down sqlite3

New submission from Erlend Egeberg Aasland : We should explicitly initialise (and shut down) the SQLite library in the sqlite3 module. This may be required in future releases: Quoting from the SQLite docs: "For maximum portability, it is recommended that applications always invoke sqlite3_ini