Install and update dependencies on first run or each command

[sg-]

In a clean environment there are many dependencies needed for tools. If neo is the entry to tools it should ensure all deps are installed as per the requirements for the version of tools. Initially this is just something like pip install -U -r requirements.txt but forward looking should install in a venv at the program level or system level depending on how tools are distributed.

[screamerbg]

Great idea. Do you think Chris H can help with this?

[bogdanm]

pip install -U -r requirements.txt

Node that this might not be a good idea at all. The libraries managed by pip are common to all the programs managed by Python (and to the Python installation itself, which sometimes has an intimate connection with pip). Which means there's a chance that executing the above command might kill even the local Python installation (that happened to me a couple of times while trying to update yotta, using a similar mechanism). I'd defer this for now until we are able to offer venvs, or at least don't execute this command automatically, but rather let the user do it manually.

[geky]

I'm seconding @bogdanm, modifying the user's global environment on innocuous commands sounds like a bad idea, especially for giving a good first impression.

Also I think we may want to keep workspace_tool stuff and scm stuff separate as much as possible, although this is debatable.

[sg-]

There is no question this should be in a venv. neo should create it, enter and install deps.

[screamerbg]

neo should call environment setup script in tools which does the job. Any volunteer to write it?

[geky]

I can look into it. Will keep this thread updated.

[screamerbg]

Now address in PR #119

[screamerbg]

PR now accepted