beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergio Fernández (JIRA) <j...@apache.org>
Subject [jira] [Updated] (BEAM-1368) Python setup should be portable to Python 3.x
Date Wed, 01 Feb 2017 08:21:51 GMT

     [ https://issues.apache.org/jira/browse/BEAM-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sergio Fernández updated BEAM-1368:
-----------------------------------
    Summary: Python setup should be portable to Python 3.x  (was: Python setups should be
portable to Python 3.x)

> Python setup should be portable to Python 3.x
> ---------------------------------------------
>
>                 Key: BEAM-1368
>                 URL: https://issues.apache.org/jira/browse/BEAM-1368
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-py
>            Reporter: Sergio Fernández
>            Assignee: Ahmet Altay
>            Priority: Trivial
>             Fix For: 0.6.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> As [~balduncle] reported at BEAM-1251:
> {quote}
> I ran into the following right away with Python 3.6.0, for example, and would like to
report issues in an appropriate manner since I imagine I'll run into more.
> {quote}
> {code:none}
> $ python setup.py sdist
> Traceback (most recent call last):
>   File "setup.py", line 38, in <module>
>     PACKAGE_VERSION = get_version()
>   File "setup.py", line 33, in get_version
>     execfile(os.path.normpath('./apache_beam/version.py'),
> NameError: name 'execfile' is not defined
> {code}
> This issues doesn't aim to make the SDK runtime compatible with Python 3.x, just trying
to fix the library setup. That's another story that will be discussed at BEAM-1251.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message