[TIP] Testing a binary distribution with Tox

André Caron andre.l.caron at gmail.com
Sat Jun 20 17:09:14 PDT 2015


Hi Rob,

Thanks for replying!

Maybe I' just still new to this thing, but isn't "usedevelop=False" the
default configuration?  I normally don't use the "usedevelop" nor the
"--develop" CLI option, so I guess I'm already doing this.

Also, it looks like Tox uses "python setup.py sdist" to generate my
package.  I would like for it to test -- in addition to "sdist" -- using
"python setup.py bdist_wheel" to make sure the binary distribution is good
to go as well.

Thanks,

André

On Thu, Jun 18, 2015 at 8:39 PM, Robert Collins <robertc at robertcollins.net>
wrote:

> On 19 June 2015 at 11:31, André Caron <andre.l.caron at gmail.com> wrote:
> > Hi all,
> >
> > I'm using Tox, which installs the package in the test environments using
> > sdist (unless running with --develop option).  This is very nice, but
> it's
> > happened that I end up with deployment errors with binary distributions.
> >
> > I've been wondering how to automate the testing of my package's binary
> > distribtion to make sure it gives the same result as the source
> distribution
> > -- at the very least on the host system -- without actually running the
> > package through PyPI.
> >
> > What are your recipes for doing this?
>
> In tox.ini
>
> usedevelop = False
>
> will change this to doing setup.py install rather than develop. That
> should be enough to flush out many more issues.
>
> -Rob
> --
> Robert Collins <rbtcollins at hp.com>
> Distinguished Technologist
> HP Converged Cloud
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20150620/3710c0fe/attachment.htm>


More information about the testing-in-python mailing list