[ 
https://issues.apache.org/jira/browse/CASSANDRA-10190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16866010#comment-16866010
 ] 

Patrick Bannister commented on CASSANDRA-10190:
-----------------------------------------------

[~djoshi3], I studied the two failures in the dtest cqlsh_tests. I was able to 
address one. For the other, I suggest we do a fresh run and see if it recurs. 
Details below for posterity.

The failure in test_writing_with_token_boundaries was a Python 3 specific bug 
in the token range calculation function in cqlshlib copyutil.py, I pushed a fix 
to the branch to address it.

The failure in test_reading_max_insert_errors was deeper than cqlshlib - it was 
a warning message from one of the Cassandra nodes about garbage collection of 
an unreleased ByteBuf in the Netty epollEventLoopGroup. The test where this 
happened intentionally causes some errors to occur with the COPY FROM command, 
so this might be an indication that we're not cleaning up properly under 
certain error conditions exercised by this test. This might be worth 
investigating, but I'd say it's not a cqlshlib issue.

> Python 3 support for cqlsh
> --------------------------
>
>                 Key: CASSANDRA-10190
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10190
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Legacy/Tools
>            Reporter: Andrew Pennebaker
>            Assignee: Patrick Bannister
>            Priority: Normal
>              Labels: cqlsh
>         Attachments: coverage_notes.txt
>
>
> Users who operate in a Python 3 environment may have trouble launching cqlsh. 
> Could we please update cqlsh's syntax to run in Python 3?
> As a workaround, users can setup pyenv, and cd to a directory with a 
> .python-version containing "2.7". But it would be nice if cqlsh supported 
> modern Python versions out of the box.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to