lsst/lsst_build is a pure python which has already been converted to use setuptools, although it still contains an eups table file. As lsstsw expects to be able to clone its repo and "setup"-it. This effectively requires lsst_-build python deps to be either eups products or fulfilled by the science-pipelines conda env. The later is awkward as lsst_build is not a sci-pipe dep nor is it distributed as an eups product and the former would present a chicken vs egg problem.
publish to pypi task list:
- (step 0: convert to pure py3 and remove usage of future)
- convert to use setuptools_scm for versioning
- configure travis deployment to pypi upon tag push
- convert lsstsw to pip install or conda install lsst_build rather than clone/setup