On Wed, Oct 7, 2015 at 6:37 PM, Erik Bray <[email protected]> wrote:
> Which, incidentally, is a great reason for installable tests :) > Not really. Doesn't matter where you have the tests. It matters where you have the code being tested. Tests being installed is a mere consequence of the location of tests. > Running in the source tree is great for development. But when > preparing a release it's great to be able to create an sdist, install > that into a virtualenv, and run `package.test()` or `python -m > package.tests` or whatever. Occasionally catches problems with the > source dist if nothing else. > As I said, I like the idea. It's just that it's not feasible right now. Lets go over the issues again: * Tests too bulky (pyca/cryptography) * Tests can't be installed at all: https://github.com/getpelican/pelican/issues/1409 * Not clear how to install test dependencies. tests_require? extras? no deps? What about version conflicts and way too many deps being installed. Dependencies are like cars, they are very useful but too many of them create problems. * Real problems like standardized test output or run protocol are not solved at all. Little benefit of doing it like this if you can't build good CI tools around this. * Workflows are under-specified. User are not guided to make quality releases on PyPI. Maybe we should have a PEP that would specify/propose some concrete solutions to all those? Thanks, -- Ionel Cristian Mărieș, http://blog.ionelmc.ro
_______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
