I don't have any objection to this, really. I know I rely on a handful of
nose plugins, and possibly others do, but those should be easy enough to
re-write. I am curious though, what's the impetus for this? Is there some
pytest feature we want that nose lacks? Is there some nosetest bug or
restriction getting in the way?

On Tue, Nov 28, 2017 at 8:34 PM, Jon Haddad <j...@jonhaddad.com> wrote:

> +1
>
> I stopped using nose a long time ago in favor of py.test.  It’s a
> significant improvement.
>
> > On Nov 28, 2017, at 10:49 AM, Michael Kjellman <kjell...@apple.com>
> wrote:
> >
> > I'd like to propose we move from nosetest to pytest for the dtests. It
> looks like nosetests is basically abandoned, the python community doesn't
> like it, it hasn't been updated since 2015, and pytest even has nosetests
> support which would help us greatly during migration (
> https://docs.pytest.org/en/latest/nose.html).
> >
> > Thoughts?
> >
> > best,
> > kjellman
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Reply via email to