QQ: why do we need these constraints files? Doesn't the minimum version in setup.py give us the assurance that the minimum version installed is the one we care about?

@software-dov

QQ: why do we need these constraints files? Doesn't the minimum version in setup.py give us the assurance that the minimum version installed is the one we care about?

We need to continue to test that our software runs with the minimum version specified in setup.py. Otherwise, as new versions of a dependency are released, our code might come to depend (unknowingly) on new features / behavior of that release, and would then break in environments where our specified minimum was installed. Our convention is to test those specified minimum versions on the "oldest" Python version we support.

E.g. if you had pushed #270 without updating setup.py, the unit-3.6 tests would have failed due to the constraint.

Codecov Report

Merging #273 (eb99b25) into master (6a43682) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##            master      #273    +/-   ##
==========================================
  Coverage   100.00%   100.00%            
==========================================
  Files           20        22     +2     
  Lines          862       963   +101     
  Branches       149       171    +22     
==========================================
+ Hits           862       963   +101     

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f35b77e...eb99b25. Read the comment docs.