[
https://issues.apache.org/jira/browse/CASSANDRA-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158640#comment-13158640
]
paul cannon commented on CASSANDRA-3457:
----------------------------------------
bq. Why that particular ordering?
No strong reason. 2.6 is just a little more likely to be found than 2.7, over
our expected set of install targets, and both 2.6 and 2.7 are little bits
faster than 2.5.
Fine with changing to something else.
> Make cqlsh look for a suitable python version
> ---------------------------------------------
>
> Key: CASSANDRA-3457
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3457
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Affects Versions: 1.0.3
> Reporter: paul cannon
> Assignee: paul cannon
> Priority: Minor
> Labels: cqlsh
> Fix For: 1.0.5
>
> Attachments: 3457.patch.txt
>
>
> On RHEL 5, which I guess we still want to support, the default "python" in
> the path is still 2.4. cqlsh does use a fair number of python features
> introduced in 2.5, like collections.defaultdict, functools.partial,
> generators. We can require RHEL 5 users to install a later python from EPEL,
> but we'd have to call it as 'python2.5', or 'python2.6', etc.
> So rather than take the time to vet everything against python2.4, we may want
> to make a wrapper script for cqlsh that checks for the existence of
> python2.7, 2.6, and 2.5, and calls the appropriate one to run the real cqlsh.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
