[
https://issues.apache.org/jira/browse/BEAM-12000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17541173#comment-17541173
]
Brian Hulette commented on BEAM-12000:
--------------------------------------
Hi [~rabernat], thanks for reaching out and linking the pangeo-forge issue,
very cool to see that Pangeo Forge is looking at Beam and xarray-beam.
As for Python 3.9, you are in luck! This is closed out because we do have 3.9
support as of Beam 2.37.0 (see the fix version on this issue, and the [release
announcement|https://beam.apache.org/blog/beam-2.37.0/]). xarray-beam was
developed last year, it might be pinned to an older version of Beam that didn't
support 3.9.
Since I see there's some discussion on
[https://github.com/pangeo-forge/pangeo-forge-recipes/issues/256] about
building a prefect/dask Beam runner, I want to ping [[email protected]] on
this. I know he's been in some discussions about building a Ray runner.
Historically most of our runner implementations have been in JVM systems (e.g.
Spark, Flink, Samza, ...), and they are able to share some infrastructure.
Perhaps there's an opportunity for collaborating on shared infrastructure for
Python-native runners.
> Support Python 3.9 in Apache Beam
> ---------------------------------
>
> Key: BEAM-12000
> URL: https://issues.apache.org/jira/browse/BEAM-12000
> Project: Beam
> Issue Type: Improvement
> Components: sdk-py-core
> Reporter: Valentyn Tymofieiev
> Assignee: Valentyn Tymofieiev
> Priority: P2
> Fix For: 2.37.0
>
> Time Spent: 32h 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
