[TIP] [Distutils] RFC: Barely minimal CI + tests + packaging in Python WAS: Guidelines for where to put tests & how to package them

Olemis Lang olemis at gmail.com
Thu Mar 11 08:22:17 PST 2010

On Thu, Mar 11, 2010 at 11:15 AM, Olemis Lang <olemis at gmail.com> wrote:
> On Thu, Mar 11, 2010 at 10:47 AM, Chris Withers <chris at simplistix.co.uk> wrote:
>> P.J. Eby wrote:
>>> At 01:34 PM 3/11/2010 +0000, Chris Withers wrote:
>>>> When I last tried using setuptools test_require stuff (in a buildout
>>>> driven pylons app, iirc) I ended up with the resulting eggs dumped in the
>>>> root of my buildout and no, the ddn't go away at the end of the test run...
>>> Interesting.  Must be an artifact of how buildout calls things, then,
>>> because setuptools drops them to the *current* directory, under
>>> circumstances that assume it's running in the setup.py directory.
>> It is, but for a develop egg, that's your checkout, and that's where the
>> testing dependency eggs get dumped!
> In order to do this in developer mode what I do is

Update (if you take a look at the real build job config, you'll notice why ;o)

> {{{
> #!sh
> virtualenv buildenv
> buildenv/bin/easy_install setuptools==dev
> buildenv/bin/easy_install unittest-xml-reporting
> buildenv/bin/easy_install ciutils
> buildenv/bin/easy_install -eb . -f http://pypi.python.org/pypi/Trac/0.11.4 Trac
> cd trac && ../buildenv/bin/python setup.py develop

cd ..

> cd trunk && ../buildenv/bin/python setup.py test -r ciutils:junitrunner

cd ..

> }}}


Featured article:
On adding Hessian (RPC) support for Trac -

More information about the testing-in-python mailing list