Arvados

source:sdk/cwl and other arvados packages that import the python SDK have a dynamic dependency rule in setup.py (when not building a released package like 1.4.3), arvados-python-client <= V where V is the prerelease version of the importing package, corresponding to the latest commit in that package.

Meanwhile, run-tests uses the following approach:

• install the current python sdk to virtualenv
• install the other python packages (and their dependencies) to virtualenv
• now that all dependencies are installed, test all python packages

The desired result is that the latest versions of all python packages are tested with the latest python SDK.

When the importing package is newer than the python SDK, it works:

• install sdk/python, 1.5.0.dev20200212153748
• install sdk/cwl, requires arvados-python-client <= 1.5.0.dev20200213025007, already satisfied

When the python SDK is newer than the importing package, it breaks:

• install sdk/python, 1.5.0.dev20200212153748
• install sdk/cwl, requires arvados-python-client <= 1.5.0.dev20200123220959, not satisfied by the installed version 1.5.0.dev20200212153748, so pip downgrades to the latest qualifying version from pypi, which is 1.4.3
• sdk/cwl, sdk/pam, tools/crunchstat-summary test suites run with python sdk 1.4.3, instead of the current version