Hi Charles, Thanks for the heads up. Looking at BEAM-2784, most of the sub-tickets are either DONE or IN PROGRESS, meaning that the futurization is almost finished, right? Should I wait a bit, and then help to port/debug the test code?
Sergei On Mon, Jul 2, 2018 at 10:43 PM Charles Chen <[email protected]> wrote: > Hi Sergei, > > Matthias and Robbe are actively working on this support. Their plan is to > futurize all relevant modules and then work on Beam Python 3 tests; this is > being tracked in https://issues.apache.org/jira/browse/BEAM-2784 and I > added https://issues.apache.org/jira/browse/BEAM-4715 as well. We can > use https://issues.apache.org/jira/browse/BEAM-1251 to coordinate, as you > suggest. > > Best, > Charles > > On Mon, Jul 2, 2018 at 1:29 PM Sergei Lebedev <[email protected]> > wrote: > >> Hello, >> >> The Beam Python SDK does not currently support Python 3. This limits the >> use of Beam itself, as well as some other projects depending on it (e.g. >> TensorFlow Model Analysis [1]). >> >> There is an ongoing effort on making the SDK Python 3-compatible (see >> e.g. [2]). However, there is no up-to-date roadmap listing all the parts >> involved and the corresponding status. Therefore my question: what would be >> a good way to coordinate the work? Should I polish the umbrella ticket [3] >> and do status updates there? >> >> I'd be happy to discuss this further either on the #beam-python Slack >> channel, or directly on the mailing list. >> >> Regards, >> Sergei >> >> [1]: https://github.com/tensorflow/model-analysis/issues/8 >> [2]: >> https://github.com/apache/beam/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+%22python+3%22 >> [3]: https://issues.apache.org/jira/browse/BEAM-1251 >> >
