[
https://issues.apache.org/jira/browse/BEAM-7060?focusedWorklogId=285507&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-285507
]
ASF GitHub Bot logged work on BEAM-7060:
----------------------------------------
Author: ASF GitHub Bot
Created on: 31/Jul/19 04:50
Start Date: 31/Jul/19 04:50
Worklog Time Spent: 10m
Work Description: chadrik commented on issue #9179: [BEAM-7060] Use
typing in type decorators of core.py
URL: https://github.com/apache/beam/pull/9179#issuecomment-516694312
Got it. Makes sense.
On Tue, Jul 30, 2019 at 2:12 AM Robert Bradshaw <notificati...@github.com>
wrote:
> core is one of those few modules that must still use the objects from
> typehints.*, so I'm fully qualifying both to make things more explicit. (As
> for why, our internal logic all still operates on beam typehints, it's just
> that now all our public APIs convert from typing to beam typehints so users
> don't have to know about that.)
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
>
<https://github.com/apache/beam/pull/9179?email_source=notifications&email_token=AAAPOE4IFEUM276FKS4LPSDQCAAZHA5CNFSM4IHQMQCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3DKTEQ#issuecomment-516336018>,
> or mute the thread
>
<https://github.com/notifications/unsubscribe-auth/AAAPOEZSC7PJ7D5DB4PAJBTQCAAZHANCNFSM4IHQMQCA>
> .
>
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 285507)
Time Spent: 5h 10m (was: 5h)
> Design Py3-compatible typehints annotation support in Beam 3.
> -------------------------------------------------------------
>
> Key: BEAM-7060
> URL: https://issues.apache.org/jira/browse/BEAM-7060
> Project: Beam
> Issue Type: Sub-task
> Components: sdk-py-core
> Reporter: Valentyn Tymofieiev
> Assignee: Udi Meiri
> Priority: Major
> Time Spent: 5h 10m
> Remaining Estimate: 0h
>
> Existing [Typehints implementaiton in
> Beam|[https://github.com/apache/beam/blob/master/sdks/python/apache_beam/typehints/
> ] heavily relies on internal details of CPython implementation, and some of
> the assumptions of this implementation broke as of Python 3.6, see for
> example: https://issues.apache.org/jira/browse/BEAM-6877, which makes
> typehints support unusable on Python 3.6 as of now. [Python 3 Kanban
> Board|https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=245&view=detail]
> lists several specific typehints-related breakages, prefixed with "TypeHints
> Py3 Error".
> We need to decide whether to:
> - Deprecate in-house typehints implementation.
> - Continue to support in-house implementation, which at this point is a stale
> code and has other known issues.
> - Attempt to use some off-the-shelf libraries for supporting
> type-annotations, like Pytype, Mypy, PyAnnotate.
> WRT to this decision we also need to plan on immediate next steps to unblock
> adoption of Beam for Python 3.6+ users. One potential option may be to have
> Beam SDK ignore any typehint annotations on Py 3.6+.
> cc: [~udim], [~altay], [~robertwb].
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
