[ 
https://issues.apache.org/jira/browse/CASSANDRA-20997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18069989#comment-18069989
 ] 

Stefan Miklosovic commented on CASSANDRA-20997:
-----------------------------------------------

I tried to do this (1), the problem seems to be that when we update "python", 
it actually does nothing effective, because I think that tests use python3 and 
it defaults to whatever it is at that time. So when I set it to "python3" 
explicitly it seems to help.

But then I also added

{{RUN update-alternatives --set python3 /usr/bin/python3.8}}

just before

{{RUN python3.8 -m pip install --upgrade pip}}

because when not set like that, then I get this:

{code}
 => ERROR [28/49] RUN virtualenv --python=python3.8 /home/cassandra/env3.8      
                                                                                
           0.3s
------
 > [28/49] RUN virtualenv --python=python3.8 /home/cassandra/env3.8:
0.302 Traceback (most recent call last):
0.302   File "/usr/bin/virtualenv", line 5, in <module>
0.302     from virtualenv.__main__ import run_with_catch
0.302   File "/usr/lib/python3/dist-packages/virtualenv/__init__.py", line 3, 
in <module>
0.302     from .run import cli_run, session_via_cli
0.302   File "/usr/lib/python3/dist-packages/virtualenv/run/__init__.py", line 
14, in <module>
0.302     from .plugin.creators import CreatorSelector
0.302   File 
"/usr/lib/python3/dist-packages/virtualenv/run/plugin/creators.py", line 6, in 
<module>
0.302     from virtualenv.create.via_global_ref.builtin.builtin_way import 
VirtualenvBuiltin
0.302   File 
"/usr/lib/python3/dist-packages/virtualenv/create/via_global_ref/builtin/builtin_way.py",
 line 7, in <module>
0.302     from virtualenv.create.creator import Creator
0.302   File "/usr/lib/python3/dist-packages/virtualenv/create/creator.py", 
line 15, in <module>
0.302     from virtualenv.discovery.cached_py_info import LogCmd
0.302   File 
"/usr/lib/python3/dist-packages/virtualenv/discovery/cached_py_info.py", line 
11, in <module>
0.302     import pipes
0.302 ModuleNotFoundError: No module named 'pipes'
------
{code}

This is because at that time, virtualenv is run with whatever python3 is set, 
which is 3.13, and it seems like there is no pipes package (2). So we installed 
virtualenv with 3.8 and then we use 3.13 where it is not.

But that is not the end of it ... you will see when you apply my commit 
yourself and try to run that command with the test as shown above.

(1) 
https://github.com/smiklosovic/cassandra/commit/38fe80815f01bab82a4537f32bfb6e24152114d7
(2) https://github.com/circus-tent/circus/issues/1215

> 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: 2h 50m
>  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]

Reply via email to