Force installation of dependencies in entry points

[theotherjimmy]

Entry points affected:

• build.py
• make.py
• test.py
• project.py

They will install every dependency within requirements.txt that cannot be found with pkg_resources.working_set.require

[sg-]

@screamerbg please review

[screamerbg]

LGTM

[0xc0170]

One question @theotherjimmy : what's the time profile for this change? How much does it take per invocation ?

Plus, I am not certain this is what is expected from a python module? I mean setup.py is an entry point, however, if we consider these tools not to have that entry point, then there should be a consumer of these tools where those req should be (dependencies) and they should follow what python modules do, you install them prior a use, or at least quick check. and a user do what is required - install via pip, install as an egg, virtualenv, etc..
How does it solve the dependency versions? I dont see that here

[screamerbg]

@0xc0170 the impact shouldn't be significant as pip install -r requirements.txt is only invoked if modules are missing. @theotherjimmy perhaps reload(site) should be part of the pip install... rather than applied every time, e.g. even if the modules are okay.