-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[Task]: Support Python 3.12 #29149
Comments
* docs(samples): Add Dataflow to Pub/Sub snippet Adds a snippet that shows how to write messages to Pub/Sub from Dataflow. * Fix region tag * Skip Python 3.12 test see apache/beam#29149 * Fix copyright date * Improve IT by reading messages from Pub/Sub * Incorporate review feedback * Fix testfor 3.8 * Fix linter error
Hey. Friendly question here. After Datastax fixed their libev support for cassandra-driver (testing it in apache/airflow#38314) , Papermill and Apache Beam are two last community Airflow Providers that have no Python 3.12 support. We are just about to release Airflow 2.9.0 where Python 3.12 support is enabled and also default airflow image is going to by Python 3.12, so Apache Beam will be uninstallable there and unusable - due to conflicting dependencies that have no Python 3.12 support (it will still work on Python 3.8 - 3.11). I looked at the 2.55.0rc3 just uploaded - and it does not seem to come with Python 3.12 support, so I'd love to know if Python 3.12 support is planned any time soon. |
This will be worked on in Q2. Thanks. |
TODO: Update all GHA tests definitions, see:
|
Looking forward to enabling apache-beam provider for Airflow to 3.12 finally ! |
After apache/beam#29149 has been fixed and Apache Beam 2.59.0 released we can finally unblock Apache Beam provider for Python 3.12 - mainly because requests is no longer limited so that Apache Beam does not conflict with few other dependencies.
What needs to happen?
Add support for Python 3.12
Issue Priority
Priority: 2 (default / most normal work should be filed as P2)
Issue Components
The text was updated successfully, but these errors were encountered: