[
https://issues.apache.org/jira/browse/CASSANDRA-20997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18059015#comment-18059015
]
Arvind Kandpal commented on CASSANDRA-20997:
--------------------------------------------
Hi, I have working on this.
As [~fmaurer] noted, simply relaxing the version check fails because the
asyncore module was removed in Python 3.12 (PEP 594), which cqlsh relies on.
My approach to fix this:
* Backport asyncore: I added asyncore.py to pylib/ so cqlsh can load it on
newer Python versions.
* Update Version Checks: Modified bin/cqlsh and bin/cqlsh.py to fully support
Python 3.12 and 3.13.
Is this approach is correct or need any other way to do ?
cc [~dnk]
> 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
> Priority: Normal
>
> 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]
