The more common pattern is to make nose, mock "extra" dependencies in the setuptools sense (as in pip install matplotlib[test]) - see the IPython setup.py and supporting functions for an example.

"extra" dependencies seem to be deprecated. I would suggest that we use tests_require to specify the test dependencies and then register a TestCommand in the setup.py. This means that upon running python setup.py test, the test requirements are installed not in the virtual environment, but as eggs in the local folder.

python setup.py test would be the standard way to invoke the nosetests (i.e. take the role of today's ./tests.py)

@HolgerPeters My understanding of the history of our setup.py and test suite is that they pre-dated many of today's standard best practices/tools and grew organically over time. This has resulted in something that works, but is a bit Frankenstein like, even by the standards of python + c-extension packaging.

If you would like to take a crack at cleaning up/modernizing/making sane the build scripts please go for it!

On the radar is also to make sure we have a working conda recipe in our repo.

This was fixed by #4188/#4668, no?

Yes they are no longer installed automatically