On Tue, Oct 6, 2015 at 10:51 AM, Antoine Pitrou <solip...@pitrou.net> wrote:
> They should be inside the module. That way, you can check an installed > module is ok by running e.g. "python -m mypackage.tests". Any other > choice makes testing installed modules more cumbersome. > Does that really make sense? I haven't heard of any user actually running tests that way. To be honest I haven't ever ran Python's own tests suite as part of a user installation. I've seen some projects that lump up lots of test data and crazy files in their packages tests and that created install issues (Pelican is one example, pretty sure there are others). On the other hand, if the user really wants to run the tests he can just get the sources (that would naturally include everything)? Seems odd to suggest something is a best practice without giving any clue of how test dependencies would be managed. Just because CPython does it doesn't mean libraries should. Thanks, -- Ionel Cristian Mărieș, http://blog.ionelmc.ro
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
