[
https://issues.apache.org/jira/browse/CASSANDRA-10190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16778833#comment-16778833
]
Patrick Bannister commented on CASSANDRA-10190:
-----------------------------------------------
I think I'll need to look at this more closely to understand what happened, but
sharing my initial intuition: I suspect this is a change in the internals of
the Python re module. The saferscanner class plays with fire by extending the
Python re.Scanner class. Scanner is supposed to be internal, not a public API
offering, and dealing with changes in re.Scanner between Python 2.7 and Python
3 was one of the first challenges I tackled in porting cqlsh to Python 3.
That's just my gut feeling looking at the stacktrace. I can look more in depth
after I do more work with this branch when CASSANDRA-14298 is merged.
> 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
> Priority: Major
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
