You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Sergei Lebedev <su...@gmail.com> on 2018/07/02 20:28:31 UTC
Python 3 support in the Python SDK
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
Re: Python 3 support in the Python SDK
Posted by Robbe Sneyders <ro...@ml6.eu>.
Hi Sergei,
We're currently finishing the futurization step. We have some open PRs,
which I see you've started reviewing. Thanks for that!
As Charles said, we will start working on the Beam Python 3 tests when the
futurization step is finished completely. We're planning to start with the
coders package again, and define a strategy to apply to all packages. I
will tag you in the related PR for discussion, and then we can coordinate
the remaining work.
Kind regards,
Robbe
On Mon, 2 Jul 2018 at 22:57 Sergei Lebedev <su...@gmail.com> wrote:
> 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 <cc...@google.com> 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 <su...@gmail.com>
>> 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
>>>
>> --
[image: https://ml6.eu] <https://ml6.eu/>
* Robbe Sneyders*
ML6 Gent
<https://www.google.be/maps/place/ML6/@51.037408,3.7044893,17z/data=!3m1!4b1!4m5!3m4!1s0x47c37161feeca14b:0xb8f72585fdd21c90!8m2!3d51.037408!4d3.706678?hl=nl>
M: +32 474 71 31 08
Re: Python 3 support in the Python SDK
Posted by Sergei Lebedev <su...@gmail.com>.
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 <cc...@google.com> 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 <su...@gmail.com>
> 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
>>
>
Re: Python 3 support in the Python SDK
Posted by Charles Chen <cc...@google.com>.
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 <su...@gmail.com> 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
>