[TIP] Best practices for testing C extensions?

Daniel Knüttel daniel.knuettel at daknuett.eu
Mon Sep 9 01:50:52 PDT 2019

Hi Florian,

> One somewhat popular solution is using the src layout:
> https://blog.ionelmc.ro/2014/05/25/python-packaging/
> https://hynek.me/articles/testing-packaging/

I always just used the same layout as my colleagues. After reading that
I won't do that anymore. The src layout seem to be pretty superior.
Also it fixed the problem with the C extensions. Thanks for that.

> You might also want to use tox as a defacto-standard instead of a
> Makefile:
> https://tox.readthedocs.io/

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. 

Your reply helped a lot; thank you very much!

Daniel Knüttel <daniel.knuettel at daknuett.eu>

More information about the testing-in-python mailing list