GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - python/cpython-source-deps: Source for packages that the cpython build process depends on

BranchesTags
Open more actions menu

Latest commit

 

History

21 Commits
21 Commits

Folders and files

NameName
Last commit message
Last commit date
README.rst
README.rst
 
 

Repository files navigation

cpython-source-deps

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 repository unless you are updating its contents.

Contents

  • Updating Source Dependencies
  • Download links
  • Tagging the commit

Updating Source Dependencies

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

  1. Fork and clone this repository.

  2. Checkout a new branch off the sqlite branch. Assuming this repo is set as your upstream:

    git checkout -b <branch-name>-sqlite upstream/sqlite
    
  3. Download SQLite source from sqlite.org.

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

  5. Commit and push the changes.

  6. Create the PR, with sqlite as the base branch.

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

For updating each project to be updated, follow the above instructions with appropriate substitutions. For sqlite, bzip2, xz, zlib-ng, and zstd, that's it!

For openssl, tcl/tk, and libffi, builds of each should also be checked into cpython-bin-deps for use in the CPython Windows build. Each one has a prepare_<name>.bat script in the cpython PCbuild directory that will take care of building the project. Note, though, that builds checked into cpython-bin-deps need to be signed by the release signing key, so it is generally up to a member of the release management team to create those builds.

Download links

  • 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-ng: https://github.com/zlib-ng/zlib-ng
  • zstd: https://github.com/facebook/zstd

Tagging the commit

Using the sqlite branch as an example:

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

About

Source for packages that the cpython build process depends on

Resources

Readme

Code of conduct

Code of conduct

Security policy

Security policy
Activity
Custom properties

Stars

31 stars

Watchers

48 watching

Forks

49 forks
Report repository

Releases

Sponsor this project

Packages

Used by

Contributors

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.