[
https://issues.apache.org/jira/browse/CASSANDRA-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16450051#comment-16450051
]
Stefan Podkowinski commented on CASSANDRA-14298:
------------------------------------------------
{quote}For example, do we want to go all the way to Python 3, or would we
prefer it to be 2/3 cross-compatible?
{quote}
Being cross-compatible would be the most convenient option for users I guess.
But I haven't really any experience converting Python 2 code in such a way.
Would you up to give this a try, Patrick?
{quote}I agree with this, only casually observing this ticket. Is it worth
bringing up on the dev@ ML?
{quote}
Sure. Maybe we can bring it up with an actual proposal after checking our
options.
{quote}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.
{quote}
Depending on how invasive those changes will turn out to be, we can discuss
patching 3.11, but I don't think that's going to happen for older branches.
Anyone running Cassandra 2.x/3.0 should be able to keep using Python 2 until
EOL 2020, which should be well past the Cassandra EOL date.
{quote}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.
{quote}
We currently run 0% tests on b.a.o. If we can get all but the copy tests
working in a straight forward way, that would be a good start.
> 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
