<div dir="ltr"><div class="gmail_quote">On Sun, Feb 13, 2011 at 10:21 PM, Tres Seaver <span dir="ltr"><<a href="mailto:tseaver@palladion.com">tseaver@palladion.com</a>></span> wrote:</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<div><div></div><div class="h5"><br>
On 02/12/2011 08:19 AM, cool-RR wrote:<br>
<br>
> What would be a good workflow to do post-release testing of my PyPI<br>
> packages? That is, I make a new release on PyPI, and I want to install it on<br>
> a VM and run the tests on the installed version. What would be a good way to<br>
> do it?<br>
<br>
</div></div>I use virtualenv, something like this::<br>
<br>
$ export WHERE=/tmp/test-yourpackage<br>
$ /path/to/python/bin/virtualenv --no-site-packages $WHERE<br>
$ $WHERE/bin/easy_install nose coverage<br>
$ $WHERE/easy_install --always-unzip yourpackage<br>
$ export TARGET=$WHERE/lib/python2.x/site-packages<br>
$ $WHERE/bin/nosetests --where=$TARGET/yourpackage-x.y-python2.x.egg<br>
<br>
<br>
Tres.</blockquote><div><br></div><div>Thanks for the suggestion. I do find it to be a bit lengthy.</div><div><br></div><div>Eventually I went with installing the `test_garlicsim` package along with `garlicsim`, and installing a `_test_garlicsim` script on the user's computer which invokes Nose with the `test_garlicsim` package.</div>
<div><br></div><div></div></div><br>
<div>Ram.</div></div>