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

Brad Schoening edited comment on CASSANDRA-17293 at 2/19/22, 3:34 AM:
----------------------------------------------------------------------

I've updated this with complete removal of nose, which was just used in two 
imports with  assert_raises 
([test_sslhandling.py|https://github.com/apache/cassandra/pull/1445/files#diff-057858697ae1e4bf6ce45a04be0f86db981a17626fc44c4d2236b11e46c7c572])
 and @nottest 
([cassconnect.py|https://github.com/apache/cassandra/pull/1445/files#diff-1b10bccb3fa32f131ec7bcc8b6b03c776e96e2176ef6431873005c3ef46abd29])


was (Author: bschoeni):
I've updated this with complete removal of nose, which was just two imports.

> Update python test framework from nose to pytest
> ------------------------------------------------
>
>                 Key: CASSANDRA-17293
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17293
>             Project: Cassandra
>          Issue Type: Task
>          Components: CQL/Interpreter
>            Reporter: Brad Schoening
>            Assignee: Brad Schoening
>            Priority: Normal
>             Fix For: 4.x
>
>
> I had trouble trying to install and run the python nose test from pip 
> (nosetest not found).
> According to the homepage of nose at [https://nose.readthedocs.io/en/latest/]
> h1. _Note to Users_
> _Nose has been in maintenance mode for the past several years and will likely 
> cease without a new person/team to take over maintainership. New projects 
> should consider using [Nose2|https://github.com/nose-devs/nose2], 
> [py.test|http://pytest.org/], or just plain unittest/unittest2._
>  
> Upgrading to pytest is likely the least effort. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to