[
https://issues.apache.org/jira/browse/CASSANDRA-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449131#comment-16449131
]
Patrick Bannister commented on CASSANDRA-14298:
-----------------------------------------------
I agree that porting C* cqlsh to Python 3 is inevitable. This ticket probably
isn't a good reason to do it, but there are other better reasons to do it, such
as the pending end of life for Python 2.
[~jasobrown], I suspect you were more asking Stefan than me, but I agree that
the question of porting cqlsh to Python 3 should be discussed on the list. It
would be worth some discussion on how to do it. For example, do we want to go
all the way to Python 3, or would we prefer it to be 2/3 cross-compatible? And,
how far back are we going to port - would we go back to 3.0, since we're still
supporting it until six months after 4.0 is released?
I suggest that if we're going to start a Python 3 epic, we should do it in a
separate ticket, and make this ticket a subticket under it.
Dialing back the scope to just the cqlsh tests - keep in mind that this problem
only impacts a third of the cqlsh copy tests. I have everything in
cqlsh_tests/cqlsh_tests.py working fine right now, nothing in that set of tests
depends on the C* cqlshlib.
However, for the impacted copy tests, we can only completely avoid these ugly
workarounds if we port cqlshlib to Python 3 not only in trunk, but also in all
other supported versions. Any branch of C* left behind on Python 2.7 will
either have to be skipped for the copy tests, or else tested through some kind
of alternate approach such as the awful hack I'm working on right now.
> cqlshlib tests broken on b.a.o
> ------------------------------
>
> Key: CASSANDRA-14298
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14298
> Project: Cassandra
> Issue Type: Bug
> Components: Build, Testing
> Reporter: Stefan Podkowinski
> Assignee: Patrick Bannister
> Priority: Major
> Attachments: cqlsh_tests_notes.md
>
>
> It appears that cqlsh-tests on builds.apache.org on all branches stopped
> working since we removed nosetests from the system environment. See e.g.
> [here|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-trunk-cqlsh-tests/458/cython=no,jdk=JDK%201.8%20(latest),label=cassandra/console].
> Looks like we either have to make nosetests available again or migrate to
> pytest as we did with dtests. Giving pytest a quick try resulted in many
> errors locally, but I haven't inspected them in detail yet.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
