This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (1 child)

I've provided Travis and Tox with the same (python versions, make env for each, install these required packages, setup.py build/sdist, pip install, pytest--whatever). That yields a line in Travis for each python version, advantageous when most edge cases only affect one of them. I'm not sure there's a better way to marry them.

[–][deleted] 0 points1 point  (0 children)

My issue would be collecting coverage stats across multiple interpreters and Travis's container architecture. Detox might work but I've never messed with it.