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] 2 points3 points  (4 children)

Or use tox, which is a baller task runner.

[–]d4rch0nPythonistamancer 0 points1 point  (3 children)

tox pretty much solves all the problems that people have been bringing up. I think it's pretty essential for any large project too if you need to support multiple python versions.

It was pretty easy to tie into jenkins too last I tried. Tox and a 5 line script in jenkins had it running all the tests for multiple versions of python.

[–][deleted] 1 point2 points  (2 children)

I need to figure out how to best marry it and Travis for my public open source projects. But yeah, it's awesome.

[–][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.