[
https://issues.apache.org/jira/browse/STORM-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186717#comment-15186717
]
ASF GitHub Bot commented on STORM-1605:
---------------------------------------
GitHub user unsleepy22 opened a pull request:
https://github.com/apache/storm/pull/1196
[STORM-1605] use '/usr/bin/env python' to check python version
Current python version check is hard-coded and it cannot detect python
2.7.x versions. Changed to /usr/bin/env to keep consistent with storm.py
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/unsleepy22/storm STORM-1605
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/1196.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 #1196
----
commit 20f1497c213c97a8a72b2f43039ad59ce9ce5169
Author: 卫乐 <[email protected]>
Date: 2016-03-09T08:05:04Z
use '/usr/bin/env python' to check python version
----
> storm shell script should use /bin/env python to check python version
> ---------------------------------------------------------------------
>
> Key: STORM-1605
> URL: https://issues.apache.org/jira/browse/STORM-1605
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core
> Affects Versions: 0.10.1, 2.0.0
> Environment: RHEL 5.7
> Reporter: Cody
> Fix For: 0.10.1, 2.0.0
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Currently storm script uses /usr/bin/python2.6 and /usr/bin/python to check
> python version, however, RHEL5 ships with python2.4 by default, so when users
> upgrade python to 2.7.5 without changing /usr/bin/python to 2.7.5 python
> binary, storm will fail to start since it thinks it's using python2.4.
> It would be better to use /bin/env python to detect python version instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
