Switch testing to pytest? #1280
Yes. That's the gist of it. And indeed, travis config would also need to be adjusted to use pytest.
Things might get complicated, though. For example because of older numpy.testing dependency on nose.
Because of the sensitivity of this kind of change, it would be good to discuss the strategy towards changing this. For example, do we want to change it all in one fell swoop, or do we envision having an intermediate stage that depends on both pytest and nose, until we can stabilize?
I made a really quick test:
Base on that, I think it will be better to avoid the intermediate stage. Of course, this is a preliminary thought, many chances that I do not see all tricky part