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, at 5:17 AM, Tomas Repik <tre...@redhat.com> 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 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 another plan? What > was the original reason for the client for Cassandra being written in python? > > Too many questions? Sorry for that, I'm just curious. My main idea was to get > involved in the discussion about cqlsh and python 3. And if there is not one > already I would like to start it. > > Tomas > > [1] https://pythonclock.org/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
