I tried running the test commands outside tox, and got <https://bitbucket.org/ned/coveragepy/issue/276/>.
Also, as I said on IRC, another problem with the tests is that they use nose, so enabling them will lead to build-dependency loop between nose and python-coverage. -- Dmitry Shachnev On Sat, Nov 16, 2013 at 1:06 PM, Ben Finney <ben+deb...@benfinney.id.au> wrote: > Howdy all, > > I'm trying to run the test suite of a packagfe I'm maintaining. Upstream > only supports running the test suite using ‘tox’: > > $ tox -e py27,py33 > > But this fails in a Debian build environment because ‘tox’ expects to > install packages from PyPI, and ignores already-installed OS packages. > > With ‘python-nose’ and ‘python-mock’ both installed, ‘tox -e py27’ still > attempts to install ‘nose’ and ‘mock’ from the internet (and fails > because I've disabled internet access in the build environment). > > How can I convince ‘tox’ to use the OS-installed packages? > > Alternatively, I don't really care about the special features of ‘tox’; > I only want to run the test suite with the specific PYthon version. What > can I do in the build environment to run the test suite as ‘tox’ would > run it? -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cakimphvqcgf_gw0xapwzwroapgd9zpfa+7pgty6h4k+ry0c...@mail.gmail.com
