I feel like the test suite should be included in the release tarball that is uploaded to pypi. Linux distributions, such as Debian, base their packages of Python modules on the pypi release. It is very useful to be able to run the test suite when building a Debian package. Running the test suite can catch mistakes in the packaging or errors introduced into dependencies.
Coverage remained the same at 100.0% when pulling e34b9ccecdf54d623a31c26ab06004c61ec4c82e on EdwardBetts:patch-1 into 72f8f0a7e0121cf5989a2cb00d5e1395e02a0445 on habnabit:master.
I feel like the test suite should be included in the release tarball that is uploaded to pypi. Linux distributions, such as Debian, base their packages of Python modules on the pypi release. It is very useful to be able to run the test suite when building a Debian package. Running the test suite can catch mistakes in the packaging or errors introduced into dependencies.
I've written a more detailed description of my thinking on the Debian Python mailing list: https://lists.debian.org/debian-python/2016/04/msg00074.html