SQLite 3.34.0 was released 2020-12-01: https://www.sqlite.org/releaselog/3_34_0.html

Compiles fine on master, and tests are completing without error.

Steve Dower: It should be fairly easy to add a CI check that validates the source checksums, so you don't need to do it manually every time. I can throw up a simple GH workflow for the sqlite branch if you want.

See attached proof-of-concept CI check. This GitHub Workflow extracts the SQLite version information, downloads the amalgamation source code, and does a simple `cmp` on each file.

Example run: https://github.com/erlend-aasland/cpython-source-deps/runs/1586069119?check_suite_focus=true

New changeset c94ee13ad596d26d1859078bc09806aa59bb0000 by Erlend Egeberg Aasland in branch 'master':
bpo-42584: Update macOS installer to use SQLite 3.34.0 (GH-23674)
https://github.com/python/cpython/commit/c94ee13ad596d26d1859078bc09806aa59bb0000

Honestly, keeping a CI run alive is more work than just doing the extract and push myself. I know this means it feels like you can't do as much yourself to speed up the integration, but it really isn't going to slow it down that much.

FWIW, any core dev can merge SQLite updates for Windows (if they're satisfied there are no issues). It's only OpenSSL that relies on running a signed build.

> FWIW, any core dev can merge SQLite updates for Windows (if they're satisfied there are no issues).

A CI check would indicate that there are no issues. The PoC CI is just a short bash script wrapped in GitHub's workflow syntax. I'd be happy to maintain it, FWIW. On the other hand, adding a CI check is not super important for me :)

https://sqlite.org/versionnumbers.html:
"[…] the current tarball naming conventions only reserve two digits for the Y and so the naming format for downloads will need to be revised in about 2030."

New changeset dd74c01d3bd2833f72ffe400a1d10b8583c0ba6a by Erlend Egeberg Aasland in branch 'master':
bpo-42584: Update Windows installer to use SQLite 3.34.0 (GH-23675)
https://github.com/python/cpython/commit/dd74c01d3bd2833f72ffe400a1d10b8583c0ba6a

Ned Deily, can you fix the macOS backports?

Steve Dower, do you mind if I create backports for the Windows build as well?

New changeset f27451dc35f1c69be0c26e8aeafee7ba6771039a by Erlend Egeberg Aasland in branch '3.8':
[3.8] bpo-42584: Update macOS installer to use SQLite 3.34.0 (GH-23674). (GH-24129)
https://github.com/python/cpython/commit/f27451dc35f1c69be0c26e8aeafee7ba6771039a

New changeset e9a71dab094c0467f07d13cce4324c8a93727863 by Erlend Egeberg Aasland in branch '3.9':
[3.9] bpo-42584: Update macOS installer to use SQLite 3.34.0 (GH-23674) (GH-24130)
https://github.com/python/cpython/commit/e9a71dab094c0467f07d13cce4324c8a93727863

> Steve Dower, do you mind if I create backports for the Windows build as well?

Sorry, I've been doing it. They're just slow because I'm getting OpenSSL done at the same time and they both keep causing merge conflicts.

New changeset 77d54710506b67e48b50bb1758fb31fc33a33c83 by Steve Dower in branch '3.9':
bpo-42584: Update Windows installer to use SQLite 3.34.0 (GH-23675)
https://github.com/python/cpython/commit/77d54710506b67e48b50bb1758fb31fc33a33c83

> Sorry, I've been doing it. They're just slow because I'm getting OpenSSL done at the same time and they both keep causing merge conflicts.

No problem. I noticed that, so I aborted my cherry-picker.

New changeset db91714faa6d3ede59003cdcc719a758160f3970 by Steve Dower in branch '3.8':
bpo-42584: Update Windows installer to use SQLite 3.34.0 (GH-23675)
https://github.com/python/cpython/commit/db91714faa6d3ede59003cdcc719a758160f3970