beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (BEAM-2784) Fix issues from automated conversion to allow Python 2 functionality
Date Fri, 01 Jun 2018 14:37:00 GMT


ASF GitHub Bot logged work on BEAM-2784:

                Author: ASF GitHub Bot
            Created on: 01/Jun/18 14:36
            Start Date: 01/Jun/18 14:36
    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
   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 at least 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:

Issue Time Tracking

    Worklog Id:     (was: 108091)
    Time Spent: 50m  (was: 40m)

> Fix issues from automated conversion to allow Python 2 functionality
> --------------------------------------------------------------------
>                 Key: BEAM-2784
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-py-core
>            Reporter: holdenk
>            Assignee: Holden Karau
>            Priority: Major
>          Time Spent: 50m
>  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

View raw message