Fix generate-constraints run on different python than base #52464
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
gopidesupavan
approved these changes
Jun 29, 2025
It turns out that when we are installing Breeze we were using the "Image" python version and not the 'default" python version to install breeze, and Python 3.12 and 3.11 are not installed by default when generate-constraints runs. This change fixes this problem, also it changes the name of the generate-constraints job to only show the python version used.
a244233 to
b7ce773
Compare
This was referenced Jun 29, 2025
|
Merging. Passed the failures. |
github-actions bot
pushed a commit
that referenced
this pull request
Jun 29, 2025
#52464) It turns out that when we are installing Breeze we were using the "Image" python version and not the 'default" python version to install breeze, and Python 3.12 and 3.11 are not installed by default when generate-constraints runs. This change fixes this problem, also it changes the name of the generate-constraints job to only show the python version used. (cherry picked from commit 33afdf9) Co-authored-by: Jarek Potiuk <[email protected]>
Backport successfully created: v3-0-test
|
potiuk
added a commit
that referenced
this pull request
Jun 29, 2025
#52464) (#52466) It turns out that when we are installing Breeze we were using the "Image" python version and not the 'default" python version to install breeze, and Python 3.12 and 3.11 are not installed by default when generate-constraints runs. This change fixes this problem, also it changes the name of the generate-constraints job to only show the python version used. (cherry picked from commit 33afdf9) Co-authored-by: Jarek Potiuk <[email protected]>
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.
It turns out that when we are installing Breeze we were using the "Image" python version and not the 'default" python version to install breeze, and Python 3.12 and 3.11 are not installed by default when generate-constraints runs.
This change fixes this problem, also it changes the name of the generate-constraints job to only show the python version used.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.