https://github.com/python/cpython-source-deps
Source for packages that the cpython build process depends on
https://github.com/python/cpython-source-deps
Last synced: 3 months ago
JSON representation
Source for packages that the cpython build process depends on
- Host: GitHub
- URL: https://github.com/python/cpython-source-deps
- Owner: python
- Created: 2017-05-22T17:20:29.000Z (about 8 years ago)
- Default Branch: main
- Last Pushed: 2024-09-24T00:29:29.000Z (9 months ago)
- Last Synced: 2024-10-29T16:02:38.177Z (8 months ago)
- Size: 101 MB
- Stars: 25
- Watchers: 55
- Forks: 43
- Open Issues: 0
-
Metadata Files:
- Readme: README.rst
Awesome Lists containing this project
README
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
----------------------------
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 -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-``.
For updating each project to be updated, follow the above instructions with
appropriate substitutions. For ``sqlite``, ``bzip2``, ``xz``, and ``zlib``,
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_.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``: https://zlib.net/
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