[
https://issues.apache.org/jira/browse/BEAM-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924884#comment-15924884
]
ASF GitHub Bot commented on BEAM-1693:
--------------------------------------
GitHub user tibkiss opened a pull request:
https://github.com/apache/beam/pull/2243
[BEAM-1693] Detect supported Python & pip executables in Python-SDK
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:
- [ ] Make sure the PR title is formatted like:
`[BEAM-<Jira issue #>] Description of pull request`
- [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
- [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
number, if there is one.
- [ ] If this contribution is large, please file an Apache
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.txt).
---
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tibkiss/beam BEAM-1693
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/2243.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2243
----
commit 5d0de97a02bfdac19448c62cbb48bea2f90ec4db
Author: Tibor Kiss <tibor.k...@gmail.com>
Date: 2017-03-14T19:51:35Z
[BEAM-1693] Detect supported 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)
