This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author erlendaasland
Recipients berker.peksag, erlendaasland, lukasz.langa
Date 2020-07-20.20:53:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Łukasz, pinging you, since you are the release manager of 3.9.

Without PR 20909, 3.9 will be released without explicitly requiring SQLite 3.7.3 ( looks for SQLite >= 3.7.2), compiling python 3.9 against SQLite 3.7.2 will fail at build time because of commit b9a0376, and it will also be possible to compile with SQLite 3.7.3 but run with pre SQLite 3.7.3 libraries, which could end up with a core dump.

With PR 20909, we explicitly state, in the docs, that SQLite 3.7.3 is required, and we explicitly check the SQLite version at configure time (, compile time (#ifdef => #error), and run time (if sqlite3_libversion_number() < ...) to prevent CPython from being configured, build, or run against unsupported SQLite versions.

I might be overestimating the severity of this issue, but I thought you would be interested this, as the release manager of 3.9 :)
Date User Action Args
2020-07-20 20:53:02erlendaaslandsetrecipients: + erlendaasland, lukasz.langa, berker.peksag
2020-07-20 20:53:02erlendaaslandsetmessageid: <>
2020-07-20 20:53:02erlendaaslandlinkissue40744 messages
2020-07-20 20:53:02erlendaaslandcreate