cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "paul cannon (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3457) Make cqlsh look for a suitable python version
Date Thu, 17 Nov 2011 17:36:51 GMT


paul cannon commented on CASSANDRA-3457:

Just a note for future reference- the opinion has been expressed that requiring EPEL for cassandra
rpms may not be an option. Might need to remove the 2.5 features from cqlsh and test it along
with the python driver on 2.4.
> Make cqlsh look for a suitable python version
> ---------------------------------------------
>                 Key: CASSANDRA-3457
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>            Reporter: paul cannon
>            Assignee: paul cannon
>            Priority: Minor
> 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:!default.jspa
For more information on JIRA, see:


View raw message