Re: Porting cqlsh to Python 3

2017-07-20 Thread J. D. Jordan
I don't think anyone is working on it. If you would like to then I would post on that ticket that you are going to take a stab at it and then go for it. I would keep any changes so they are working on 2.7 and 3.0 as many of the in use Linux distributions still default to 2.7. > On Jul 20, 2017,

Re: Porting cqlsh to Python 3

2017-07-20 Thread Tomas Repik
Yeah thanks, I've seen this issue on jira, but it is pretty outdated, and I wondered if there are any other means of discussing the topic other than the old jira. - Original Message - > Related: https://issues.apache.org/jira/browse/CASSANDRA-10190 >

Re: Porting cqlsh to Python 3

2017-07-20 Thread Murukesh Mohanan
Related: https://issues.apache.org/jira/browse/CASSANDRA-10190 On 2017-07-20 18:17 (+0900), Tomas Repik wrote: > Hi, > > the clock for Python 2.7 is ticking [1], and yes, there are still more than > two years, but sooner or later cqlsh should be ported to Python 3. Is

Porting cqlsh to Python 3

2017-07-20 Thread Tomas Repik
Hi, the clock for Python 2.7 is ticking [1], and yes, there are still more than two years, but sooner or later cqlsh should be ported to Python 3. Is anybody already working on it or just considers to work on it? What is the long time plan for cqlsh? Should it be in Python forever or is the