You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "paul cannon (Updated) (JIRA)" <ji...@apache.org> on 2011/11/28 19:37:39 UTC
[jira] [Updated] (CASSANDRA-3457) Make cqlsh look for a suitable
python version
[ https://issues.apache.org/jira/browse/CASSANDRA-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon updated CASSANDRA-3457:
-----------------------------------
Attachment: 3457.patch.txt
> 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
> Reporter: paul cannon
> Assignee: paul cannon
> Priority: Minor
> 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