-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Add Python 3.10 support #22050
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Python 3.10 support #22050
Conversation
|
I think we should be close to get Python 3.10 support. Let's see |
4a2a616 to
b92fda0
Compare
|
In order to generate constraints, I need to release a new wave of providers to PyPI now. And We should be good. |
b92fda0 to
102848f
Compare
|
Should we remove user warning? Lines 38 to 43 in 6db9b00
|
Yep. That too :) |
102848f to
d3aa026
Compare
|
@potiuk Do I have to make changes in Breeze2 to support Python 3.10? |
No need. I made a "bulk" update here and I also updated |
1240212 to
d0f1871
Compare
d0f1871 to
77ebb39
Compare
|
We might need to reimplement a small issue in cgroupspy - one of the few last remaining issues for Python 3.10 - see cloudsigma/cgroupspy#13 |
This is just importing existing cgroupspy library without code modifications. In the next step we will modify the cgroupspy code to work from the new location, then we will fix it to implement Python 3.10 compatibility and finally we will change airflow to use the vendored package instead of the original package. This is part of the effort needed to implement Python 3.10 compatibility: #22050
This commit applies import fixes to vendored cgroupspy library so that the library uses the vendored version internally. This commit will need to be re-applied if we upgrade the vendored cgroupspy library. This is part of the effort needed to implement Python 3.10 compatibility: apache#22050
The cgrouppspy is not Python 3.10 compliant due to Iterable being imported directly from collections. This is captured in cloudsigma/cgroupspy#13 We fix it in our vendored-in version of cgroupspy until hopefully new version of it is released. This is part of the effort needed to implement Python 3.10 compatibility: apache#22050
7a20762 to
740f3c9
Compare
This commit applies import fixes to vendored cgroupspy library so that the library uses the vendored version internally. This commit will need to be re-applied if we upgrade the vendored cgroupspy library. This is part of the effort needed to implement Python 3.10 compatibility: #22050
The cgrouppspy is not Python 3.10 compliant due to Iterable being imported directly from collections. This is captured in cloudsigma/cgroupspy#13 We fix it in our vendored-in version of cgroupspy until hopefully new version of it is released. This is part of the effort needed to implement Python 3.10 compatibility: apache#22050
This is part of the effort needed to implement Python 3.10 compatibility: apache#22050
740f3c9 to
03bcfea
Compare
The cgrouppspy is not Python 3.10 compliant due to Iterable being imported directly from collections. This is captured in cloudsigma/cgroupspy#13 We fix it in our vendored-in version of cgroupspy until hopefully new version of it is released. This is part of the effort needed to implement Python 3.10 compatibility: #22050
This is part of the effort needed to implement Python 3.10 compatibility: apache#22050
This is part of the effort needed to implement Python 3.10 compatibility: #22050
03bcfea to
6bc53a4
Compare
|
Final PR to get Python 3.10 support ! |
Python 3.10 support has been long missing because a number of our dependencies had problems with it. It seems that last problems remaining should be fixed now, and we should be able to get a proper Python 3.10 support. Closes: apache#19059
6bc53a4 to
9c140ce
Compare
Python 3.10 support has been long missing because a number of our
dependencies had problems with it. It seems that last problems
remaining should be fixed now, and we should be able to get
a proper Python 3.10 support.
Closes: #19059
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 UPDATING.md.