+1nb, Never been that fond of nose from a usability perspective, and I
wouldn't be surprised if at least some of the problems running dtests were
related to issues in nose. I can't imagine it would be a lot of work to
port to py.test, if someone wants to do it they can go right ahead.
On 29 Novemb
s/handling/hanging
> On Nov 29, 2017, at 9:54 AM, Michael Kjellman
> wrote:
>
> i keep seeing nose randomly handing after a test successfully completes
> execution. i’m very far from a python guru but i spent a few hours with gdb
> trying to debug the thing and get python stacks and got symbo
i keep seeing nose randomly handing after a test successfully completes
execution. i’m very far from a python guru but i spent a few hours with gdb
trying to debug the thing and get python stacks and got symbolicated native
stacks but it’s random but root causing while nose is sitting on a lock
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
restrict
+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 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
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.or
