[
https://issues.apache.org/jira/browse/CASSANDRA-19467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-19467:
----------------------------------------
Source Control Link:
https://github.com/apache/cassandra/commit/8a33f323508dab061dbebfd168e431cd0e683e01
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed to 5.0 as
https://github.com/apache/cassandra/commit/8a33f323508dab061dbebfd168e431cd0e683e01
> Deprecate Python 3.7 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
>
> Attachments: ci_summary.html
>
>
> 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.7 (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.7 until our
> 6.0 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
