I did a lot of work to make cqlsh compatible with Python 3 (and also Python
2.7) under CASSANDRA-10190. CASSANDRA-10190 has been blocked by
CASSANDRA-14298, which got about two thirds of the cqlsh dtests to work.
If somebody could commit to reviewing CASSANDRA-14298, I'd be willing to
pick it
I saw that thread and the tickets. They haven't had any activity recently.
Given that it is already Feb 2019 and Python 2.7 is getting close to EOL'd, I
think it's worth moving forward with deprecating Python 2.7 support and adding
3.0 support prior to 4.0 release. I am not sure what the
Previous discussion can be found here:
https://lists.apache.org/thread.html/cbc50f5ac085ac759b52eb7e87277a3b82e2773c6d507c4b525d@%3Cdev.cassandra.apache.org%3E
On 11.02.19 19:58, Ariel Weisberg wrote:
Hi,
Do you mean Python 2/3 compatibility?
This has been discussed earlier and I think
Hi,
Do you mean Python 2/3 compatibility?
This has been discussed earlier and I think that being compatible with both is
an easier sell.
Ariel
> On Feb 11, 2019, at 1:24 PM, dinesh.jo...@yahoo.com.INVALID
> wrote:
>
> Hey all,
> We've gotten the cqlsh tests running in the Cassandra repo
Hey all,
We've gotten the cqlsh tests running in the Cassandra repo (these are distinct
from the cqlsh tests in dtests repo). They're in Python 2.7 and using the
nosetests. We'd like to make them consistent with the rest of the tests which
means moving them to Python 3 & Pytest framework.
