[TIP] Best practices for testing C extensions?
me at the-compiler.org
Mon Sep 9 01:55:13 PDT 2019
On Mon, Sep 09, 2019 at 10:50:52AM +0200, Daniel Knüttel wrote:
> tox seems to be the way to go. I am not quite sure about all its
> behaviour, but I will use it from now on. Do you know if it forces new
> builds for every tox invocations? That was a big problem before, as
> setup.py does not watch C source files and does not re-build them. So I
> tested against outdated modules for a couple of hours.
I think it basically creates a virtualenv and runs setup.py. So if your
setup.py somehow builds stale libraries (which sounds odd!), that'll likely
happen with tox as well.
https://www.qutebrowser.org | me at the-compiler.org (Mail/XMPP)
GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
I love long mails! | https://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 833 bytes
Desc: not available
More information about the testing-in-python