[
https://issues.apache.org/jira/browse/BEAM-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Kiss updated BEAM-1693:
-----------------------------
Summary: Detect supported Python & pip executables in Python-SDK (was:
Detect suitable Python & pip executables in Python-SDK)
> Detect supported Python & pip executables in Python-SDK
> -------------------------------------------------------
>
> Key: BEAM-1693
> URL: https://issues.apache.org/jira/browse/BEAM-1693
> Project: Beam
> Issue Type: Improvement
> Components: sdk-py
> Reporter: Tibor Kiss
> Assignee: Tibor Kiss
>
> Python SDK currently supports Python-2.7 only.
> The Python interpreter & pip definition in pom.xml points to {{python2}} &
> {{pip2}} respectively.
> Users with multiple Python interpreters installed might end up having python2
> and pip2 pointing to their 2.6 installation. (This scenario happens mostly on
> OS X machines.)
> There is no single, valid name for the executables as different OSes install
> those binaries in various names:
> - CentOS6/EPEL: pip (python 2.6) & pip2 (python 2.6) & pip2.6 (python 2.6)
> - CentOS7/EPEL: pip (python 2.7) & pip2 (python 2.7) & pip2.7 (python 2.7)
> - Debian7: pip (python 2.7) & pip-2.6 (python 2.6) & pip-2.7 (python 2.7)
> - Debian8: pip (python 2.7) & pip2 (python 2.7)
> - Debian9: pip (python 2.7) & pip2 (python 2.7)
> - Ubuntu1204: pip (python 2.7)
> - Ubuntu1404: pip2 (python 2.7)
> - Ubuntu1604: pip (python 2.7) & pip2 (python 2.7)
> - OS X: pip (python 2.6) & pip2 (python 2.6) & pip2.7 (brew / python 2.7)
> - Windows: pip-2.7 (python.org based installer)
> To overcome this problem the pom.xml should be extended to determine the
> suitable Python interpreter & pip automatically, in a platform independent
> way.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
