Downgrade our python version when building binary files #402
Conversation
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
heyronhay
approved these changes
Nov 4, 2025
michael-richey
deleted the
michael.richey/downgrade-python-for-binaries
branch
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.
What does this PR do?
Build releases with an older version of python so that it links to an older version of glibc which should allow it to run on older images.
Description of the Change
Python 3.12 -> 3.11
Alternate Designs
Statically linking GLIBC - rejected as a first pass since it's not recommended and unlikely to work
Upgrading internal images - likely time consuming and don't want to force upgrades on users