Products must not depend on anaconda

Hi @Joshua Hoblitt,

It's difficult to be sure that all "supported" distribution will provide correct version of our python deps, on the other hand, using eups might lead to use of deprecated and non supported deps. virtualenv might not be compliant with eups... So for now I'll stick with the current way we manage dependencies, but I think in production we'll need to use systems deps or at least up-to-date deps.

Cheers,

merged

The requests product has been updated to 2.9.1 and added to repos.yaml. The PR has been updated to add requests as a dep and CI passes:

https://ci.lsst.codes/job/qserv-os-matrix/3944/

@fritz requested on HC that the version of the requests package be updated and that it be added to the qserv eups table file in place of anaconda.

My understanding from @frossie is that qserv team is OK with considering requests a "system dep", in the context for qserv_distrib, is that correct?

If so, there's a couple of different ways of fulfilling that. I suspect that eventually, the best course will be some sort of virtualenv-ish setup that makes it easy to add new python deps. In the mean time, I suggest adding something along the lines of apt-get install -qq -y python python-dev python-setuptools python-yaml python-requests python-sqlalchemy to the qserv docker files. @Fabrice Jammes, do you have any thoughts on how python deps should be handled?