You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Holden Karau <ho...@pigscanfly.ca> on 2018/02/28 00:53:34 UTC
Python 3 flake 8: splitting up on the errors?
How would folks feel about splitting up some of the Python 3 migration work
by the different flake8 errors in Py3? This might allow us to parallelize
some of the work while still keeping things fairly small?
--
Twitter: https://twitter.com/holdenkarau
Re: Python 3 flake 8: splitting up on the errors?
Posted by Holden Karau <ho...@gmail.com>.
Awesome, I'll get that kicked off in JIRA
On Feb 28, 2018 2:43 PM, "Ahmet Altay" <al...@google.com> wrote:
> I think this is a great idea. I would encourage everyone who would like to
> help with Python 3 migration to help with this effort. Holden, if you
> already have a list, could you either share the list or create individual
> JIRAs so that we can track the work among us.
>
> On Tue, Feb 27, 2018 at 4:53 PM, Holden Karau <ho...@pigscanfly.ca>
> wrote:
>
>> How would folks feel about splitting up some of the Python 3 migration
>> work by the different flake8 errors in Py3? This might allow us to
>> parallelize some of the work while still keeping things fairly small?
>>
>> --
>> Twitter: https://twitter.com/holdenkarau
>>
>
>
Re: Python 3 flake 8: splitting up on the errors?
Posted by Ahmet Altay <al...@google.com>.
I think this is a great idea. I would encourage everyone who would like to
help with Python 3 migration to help with this effort. Holden, if you
already have a list, could you either share the list or create individual
JIRAs so that we can track the work among us.
On Tue, Feb 27, 2018 at 4:53 PM, Holden Karau <ho...@pigscanfly.ca> wrote:
> How would folks feel about splitting up some of the Python 3 migration
> work by the different flake8 errors in Py3? This might allow us to
> parallelize some of the work while still keeping things fairly small?
>
> --
> Twitter: https://twitter.com/holdenkarau
>