Repository files navigation

Source for packages that the CPython build process depends on.

It is currently expected that this will only be useful on Windows,and in any case you should never need to clone this repositoryunless you are updating its contents.

The procedure for updating the different source dependencies are similar. Belowis an example for updating SQLite:

1. Fork and clone this repository.

2. Checkout a new branch off thesqlite branch. Assuming this repo is setas yourupstream:

   git checkout -b <branch-name>-sqlite upstream/sqlite

3. Download SQLite source fromsqlite.org.

4. Unzip it to the branch checked out in step 2.

5. Commit and push the changes.

6. Create the PR, withsqlite as the base branch.

Once the PR has been merged, tag the commit assqlite-<full version to be used in CPython's PCbuild/get_externals.bat>.

For updating each project to be updated, follow the above instructions withappropriate substitutions. Forsqlite,bzip2,xz,zlib, andzstd, that's it!

Foropenssl,tcl/tk, andlibffi, builds of each should also bechecked intocpython-bin-depsfor use in the CPython Windows build. Each one has aprepare_<name>.batscript in thecpythonPCbuild directory that will take care of buildingthe project. Note, though, that builds checked intocpython-bin-deps needto be signed by the release signing key, so it is generally up to a member ofthe release management team to create those builds.

• bzip2:https://www.sourceware.org/bzip2/downloads.html
• libffi :https://github.com/libffi/libffi
• mpdecimal :https://www.bytereef.org/mpdecimal/download.html
• openssl:https://www.openssl.org/source/
• sqlite:https://www.sqlite.org/download.html
• tcl/tk:https://tcl.tk/software/tcltk/download.html
• xz:https://github.com/tukaani-project/xz
• zlib:https://zlib.net/
• zstd:https://github.com/facebook/zstd

Using thesqlite branch as an example:

git checkout -b sqlite-tag upstream/sqlitegit tag sqlite-3.21.0.0  # replace 3.21.0.0 with the correct version.git push --tags upstream