You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (Jira)" <ji...@apache.org> on 2024/03/16 00:06:00 UTC
[jira] [Commented] (CASSANDRA-19467) Deprecate Python 3.8 and earlier, but allow cqlsh to run with Python 3.6+
[ https://issues.apache.org/jira/browse/CASSANDRA-19467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827623#comment-17827623 ]
Brandon Williams commented on CASSANDRA-19467:
----------------------------------------------
[Here|https://app.circleci.com/pipelines/github/driftx/cassandra/1527/workflows/cdf7af56-4afa-4c60-b5a5-2ae289c271e3] is circle on everything python.
> Deprecate Python 3.8 and earlier, but allow cqlsh to run with Python 3.6+
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-19467
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19467
> Project: Cassandra
> Issue Type: Task
> Components: Tool/cqlsh
> Reporter: Caleb Rackliffe
> Assignee: Caleb Rackliffe
> Priority: Normal
> Fix For: 5.0-rc, 5.1
>
>
> In 4.0, we introduced Python 3.6 support. In CASSANDRA-19245, for the 5.0 release, we dropped Python 3.6 and 3.7 support since Python 3.8 was the minimum supported version for version 3.29.0 of the Python driver, which we needed to support vectors. Unfortunately, that may break existing users of RHEL 7, which natively only supports Python 3.6.
> We should deprecate Python 3.6-3.8 (which are all either EOL or will be soon) and mention this in NEWS.txt/appropriate warnings at {{cqlsh}} startup, but we don't need to have cqlsh refuse to start entirely with 3.6-3.8 until our 6.0 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org