Should catkin_pip bring along it s dependencies ?

[asmodehn]

Like python-pytest... I was naively assuming that catkin_pip would install all the dependencies used most of the time...

Maybe we should focus on the python packaging guide to install these "official" tools, but let the user specify other tools if he wants to ?

[asmodehn]

another idea : maybe these should be "extra" addons to catkin & catkin_pip
=> one addon per extra tool not used in catkin (ex. pytest), but basic catkin_pip override all catkin_tools (ex. nose)

[asmodehn]

Maybe the best way is to have a catkin_pip_env_install() command that will, from cmake script at configuration, install packages from pip into catkin_pip_env. and we call that from the other functions that need it...
We probably need a bunch of requirements files...