jrmccluskey commented on issue #36478: URL: https://github.com/apache/beam/issues/36478#issuecomment-3548598530
Removing 3.9 support is not really a prerequisite for supporting 3.14/3.14t, it's just normal housekeeping with 3.9 reaching EOL and dependencies starting to drop support themselves. That effort is also done at this point, the Beam 2.70 release will not support Python 3.9. As for mainline 3.14 support, extras like tensorflow supporting 3.14 are not necessarily a problem for us as far as getting Beam itself to support the version. The only real hurdle is having core Beam and its dependencies supporting the version, with common extras largely just preventing us from rolling out expansive testing or publishing containers. This happened this year with apitools and Python 3.13, Beam itself supported the version for months (and users could work with Python 3.13 locally pretty easily) but GCP dependencies tied to apitools didn't work, so we couldn't run any common postcommit integration tests with Dataflow. We only "fully" supported 3.13 once apitools cut a release. Separately, the work to support free-threading within beam can be based on 3.13t (which has the same dependency issues as 3.14t) so we don't necessarily need 3.14 support _anyway_. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
