Add flit-core as wheel to pip bundle#114
Merged
Merged
Conversation
kiril-keranov
approved these changes
Jul 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add flit-core as wheel to pip bundle (required by pip 26.x build backend)
Problem
pip 26.x switched its build backend from setuptools to flit-core, requiring
flit-core>=3.11,<4as a build dependency. When the Python buildpack installs pip from the bundle tarball using:pip tries to install its build dependencies from /tmp/pip, but the bundle only contained pip's own source tarball — not flit-core. This caused staging to fail with:
Fix
Add
flit-core>=3.11toExtraDepsinPipRecipe.ExtraDepsare downloaded without--no-binary :all:, so flit-core is fetched as a pre-built wheel (flit_core-x.x.x-py3-none-any.whl). This breaks the circular dependency (flit-core source requires flit-core to build) and makes it available in /tmp/pip for pip to use as its build backend.Testing
Rebuild the pip 26.x bundle using binary-builder and verify staging a Python app with
PIP_VERSION=latestsucceeds on cflinuxfs4/cflinuxfs5.Fixes: cloudfoundry/python-buildpack#1200