@bear Not sure if there's a better way to do this, but this is a first stab at getting this up and running on CircleCI 2.0.
I had some issues with using separate docker containers for running tests for each supported version. Basically what I was finding was that, if you use a bunch of different containers - circleci/python:2.7 and :3.6 or whatever - we wouldn't capture the correct coverage stats.
So anyway, I made a docker image that has pyenv installed along with all the supported versions (py27, py37, pypy2 & 3) and use that as the base testing image. I couldn't find any good information on how to test multiple versions of python on CircleCI 2, so let me know if I'm reinventing the wheel here (wouldn't be the first time :) ).
Also included the Dockerfile so that as versions change it's included in the codebase and easy to rebuild. (I'm not a huge docker user, so if this is a giant rat's nest, please say so!)
@bear Not sure if there's a better way to do this, but this is a first stab at getting this up and running on CircleCI 2.0.
I had some issues with using separate docker containers for running tests for each supported version. Basically what I was finding was that, if you use a bunch of different containers - circleci/python:2.7 and :3.6 or whatever - we wouldn't capture the correct coverage stats.
So anyway, I made a docker image that has pyenv installed along with all the supported versions (py27, py37, pypy2 & 3) and use that as the base testing image. I couldn't find any good information on how to test multiple versions of python on CircleCI 2, so let me know if I'm reinventing the wheel here (wouldn't be the first time :) ).
This change is