Currently each time the target virtualenv is created, some testing tools as well as the project's dependencies must be fetched from the network.
Ideally I'd like to see two different commands: "prepare" and "run". The first uses the network to fetch test and dependency packages (probably caching them under ~/.onslaught/results/${PROJECT} somewhere. The "run" command would never use the network.
This seems like it should be a general pip feature, but I have not yet found it.
One way to solve this bug without modifying pip is to distribute the target test dependencies package files as data files within this package, and to pass their local paths directly to pip install.
Currently each time the target virtualenv is created, some testing tools as well as the project's dependencies must be fetched from the network.
Ideally I'd like to see two different commands: "prepare" and "run". The first uses the network to fetch test and dependency packages (probably caching them under
~/.onslaught/results/${PROJECT}
somewhere. The "run" command would never use the network.This seems like it should be a general pip feature, but I have not yet found it.