[
https://issues.apache.org/jira/browse/CASSANDRA-16414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17282523#comment-17282523
]
Adam Holmberg commented on CASSANDRA-16414:
-------------------------------------------
I did a bit of exploration on this. Didn't find a definitive decision anywhere,
but folks were talking about 3.6 in CASSANDRA-10190.
I found that cqlsh literally [won't
load|https://github.com/apache/cassandra/blob/902e05603b9658d7c1c3e9f02a39a771fee2708a/pylib/cqlshlib/saferscanner.py#L70]
in 3.5. That, combined with the
[check|https://github.com/apache/cassandra/blob/902e05603b9658d7c1c3e9f02a39a771fee2708a/bin/cqlsh#L66]
in the startup script led me to believe that 3.6 is (and has been) the floor,
despite the open-ended
[check|https://github.com/apache/cassandra/blob/902e05603b9658d7c1c3e9f02a39a771fee2708a/bin/cqlsh.py#L24]
that was left around in the vestigial startup code, which I believe is dead
code.
> Remove Claim of Support for Python2 in 4.0
> ------------------------------------------
>
> Key: CASSANDRA-16414
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16414
> Project: Cassandra
> Issue Type: Task
> Components: Tool/cqlsh
> Reporter: Adam Holmberg
> Assignee: Adam Holmberg
> Priority: Normal
> Fix For: 4.0-rc
>
>
> Remove claim of Python2 support in user-facing artifacts, and introduce
> warning while using Python2 with cqlsh.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
