CI: Use pip and setuptools to install pycalphad instead of Anaconda #331
@@ Coverage Diff @@ ## develop #331 +/- ## =========================================== - Coverage 87.34% 84.52% -2.83% =========================================== Files 46 46 Lines 4521 4524 +3 =========================================== - Hits 3949 3824 -125 - Misses 572 700 +128
For coverage, the code getting covered are in
Our options are
1) Pass the site package path to coverage
coverage has support for this in that we need to specify the
However, the tricky aspect is that both these examples assume some kind of local virtual environment where the site packages directory can be found within the local directory. The way it's set up, it's installed to wherever on the machine (platform dependent) the site packages are installed. Since I don't think it's possible to be able to set that path for any machine from a global config file, we need to have some kind of local environment, so either a tool like
Note that this method still allows for coverage to be run on the local
2) Test the local package instead of or in addition to the installed version
Maybe we just add another CI task specfically for coverage that uses a smaller build matrix and tests against the local version? We'd just need to decide which platforms and versions of Python to test.
My preference is for option 1) and setting up a virtual environment using the built-in
I ended up going the virtual environment route and put the requiste coverage.py settings in pyproject.toml (also moved our pytest settings over from setup.cfg).
Seems like we no longer cover
Do we want to make a decision here on depending on