[
https://issues.apache.org/jira/browse/BEAM-2784?focusedWorklogId=108089&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-108089
]
ASF GitHub Bot logged work on BEAM-2784:
----------------------------------------
Author: ASF GitHub Bot
Created on: 01/Jun/18 14:35
Start Date: 01/Jun/18 14:35
Worklog Time Spent: 10m
Work Description: cclauss commented on issue #3772: [WIP][BEAM-2784] Run
python 2 to 3 migration and fix resulting Python 2 errors
URL: https://github.com/apache/beam/pull/3772#issuecomment-393899969
My sense is that most of this has been fixed in other PRs that have already
been merged and in these four open PRs:
- [ ] #4774
- [ ] #4820
- [ ] #5310
- [ ] #5531
Given the number of conflicts, does it make sense to close this PR or rebase
it?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 108089)
Time Spent: 40m (was: 0.5h)
> Fix issues from automated conversion to allow Python 2 functionality
> --------------------------------------------------------------------
>
> Key: BEAM-2784
> URL: https://issues.apache.org/jira/browse/BEAM-2784
> Project: Beam
> Issue Type: Improvement
> Components: sdk-py-core
> Reporter: holdenk
> Assignee: Holden Karau
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> As part of BEAM-1251 we want to move to support a Python2/3 code base. To do
> this we can use futurize but futurize will break some Python2 elements. A
> good intermediate checkpoint is contiuing to support Python 2 after
> futurization from which we can build Python 3 support on top of.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
