Adding Python 2/3 compatibility to elm and earthio revealed some low-hanging fruit for how we might speed up the CI builds. One of the biggest steps we can take here is to avoid using conda-build on earthio when testing elm; instead we can either "just" conda-install the latest development version of earthio, or (as a potentially faster option) we can install earthio from source with python setup.py install. I plan to add both of these as options, controlled by an environment variable.
The other refactoring we can add is to include the py.test commands into the conda-build process, so that packages aren't successfully built nor accidentally uploaded unless they pass all tests.
I plan to address each of these issues in one PR, after PR #168 (addressing Issue #154) is merged.
Adding Python 2/3 compatibility to
elm
andearthio
revealed some low-hanging fruit for how we might speed up the CI builds. One of the biggest steps we can take here is to avoid usingconda-build
onearthio
when testingelm
; instead we can either "just"conda-install
the latest development version ofearthio
, or (as a potentially faster option) we can installearthio
from source withpython setup.py install
. I plan to add both of these as options, controlled by an environment variable.The other refactoring we can add is to include the
py.test
commands into theconda-build
process, so that packages aren't successfully built nor accidentally uploaded unless they pass all tests.I plan to address each of these issues in one PR, after PR #168 (addressing Issue #154) is merged.