Exclude ray in google provider for Python 3.13 #51994
Merged
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
boring-cyborg
bot
added
area:providers
provider:google
eladkal
approved these changes
Jun 21, 2025
Member
Author
|
We will need to merge this one and release google provider with it in order to have "generate PyPI constraints" work for Python 3.13 - #46891 |
gopidesupavan
approved these changes
Jun 21, 2025
jscheffl
approved these changes
Jun 21, 2025
Contributor
jscheffl
left a comment
jscheffl
left a comment
There was a problem hiding this comment.
Will operators or logic "fail" if ray is not installed at runtime such that we need to have some safeguards in operators? (Not that it fails in import errors and users might be confused about root cause)
Member
Author
Good point. I think I added optional Feature Exception in the 3.13 so I have to do it here as well |
Currently we cannot generate `pypi` constraint for Python 3.13, because released google provider has `ray` as dependency and `ray` does not support Pyton 3.13 yet - so we have to exclude `ray` in released provider before we can merge Python 3.13 support.
potiuk
force-pushed
the
exclude-ray-from-python-3-13
branch
from
e1b7afe to
4b92a6f
Compare
hussein-awala
approved these changes
Jun 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Currently we cannot generate
pypiconstraint for Python 3.13, because released google provider hasrayas dependency andraydoes not support Pyton 3.13 yet - so we have to excluderayin released provider before we can merge Python 3.13support.
^ 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.