On Sep 09, 2014, at 07:59 AM, Matthias Klose wrote: >it is my understanding that tox serves two purposes, one is a testing >framework, the other doing the testing in a virtual environment.
I'd agree with that. The really interesting bits for build-deps I think is the ability to test under multiple versions of Python, and to provide a one-command no-guesswork invocation of the test suite. What I mean by that is that if you see a tox.ini, you know you can run `tox` and not worry about all the various crazy things people do to run their test suite (and there's *a lot* of variation there). Sadly, my suggestions to add official metadata for test suite support to the various PEPs has not been accepted. >testing in a virtual environment makes sense as long as you don't know >your environment, however this is not the case on a buildd or an autopkg >test, where the environment is defined by the build dependencies or the >test dependencies. Agreed that the "testing in a virtual environment" is the least interesting aspect of tox as it relates to building Ubuntu packages. Unfortunately there's no way to separate out those two aspects of tox. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349832 Title: [MIR] dependencies for tox - See LP: #1367016 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distlib/+bug/1349832/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
