[
https://issues.apache.org/jira/browse/CASSANDRA-20997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18066622#comment-18066622
]
Brad Schoening commented on CASSANDRA-20997:
--------------------------------------------
Would very much like to see trunk aligned with the python driver which is 3.10+.
When 3.6 was re-added in March 2024 with
[CASSANDRA-19467|https://issues.apache.org/jira/browse/CASSANDRA-19467]the
comment was:
{noformat}
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.
{noformat}
> Support Python 3.13
> -------------------
>
> Key: CASSANDRA-20997
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20997
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Build, Dependencies, Tool/cqlsh
> Reporter: fmaurer
> Assignee: Arvind Kandpal
> Priority: Normal
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Using the cassandra install for debian using the latest deb of 5.0.6, the
> database does not come up with JDK-21:
> {{java.lang.UnsupportedOperationException: The Security Manager is deprecated
> and will be removed in a future release}}
>
> This can be fixed with
> {{JVM_EXTRA_OPTS="$JVM_EXTRA_OPTS -Djava.security.manager=allow"}}
> {{in /etc/cassandra/cassandra-env.sh}}
> then after {{systemctl restart cassandra}}
> the `cqlsh` fails with
> {{Warning: unsupported version of Python, required 3.6-3.11 but found 3.13}}
> {{No appropriate Python interpreter found.}}
>
> I would like to see a project of this size to support a more recent
> technology stack as well.
> Is there any plan to fix these issues? Thanks!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
