How to run upstream test suite that uses ‘tox’?

2013-11-16 Thread Ben Finney
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?

-- 
 \“Consider the daffodil. And while you're doing that, I'll be |
  `\  over here, looking through your stuff.” —Jack Handey |
_o__)  |
Ben Finney


-- 
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/7wk3g8vhpt@benfinney.id.au



Re: How to run upstream test suite that uses ‘tox’?

2013-11-16 Thread Vincent Bernat
 ❦ 16 novembre 2013 10:06 CET, Ben Finney  :

> 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?

You could just run the command specified in tox.ini, eg "python setup.py test".
-- 
 /*
  * Hash table gook..
  */
2.4.0-test2 /usr/src/linux/fs/buffer.c


signature.asc
Description: PGP signature


Re: How to run upstream test suite that uses ‘tox’?

2013-11-16 Thread Ben Finney
Vincent Bernat  writes:

> You could just run the command specified in tox.ini, eg "python setup.py 
> test".

Okay. I'll need to request upstream de-couple the test commands (there
are several commands specified in ‘tox.ini’) from ‘tox’.

Where should I direct upstream to read about ‘setup.py test’? Is that
the recommended way to enable a test suite for Debian and other
distributors?

-- 
 \   “The cost of education is trivial compared to the cost of |
  `\ ignorance.” —Thomas Jefferson |
_o__)  |
Ben Finney


-- 
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/7weh6gumvi@benfinney.id.au