There is a class of known problems with moving around virtualenvs, not the least of which is that it doesn't work if the same python version isn't installed in the same place between the build machine and Storm machine.
It is possible that doing the following instead of including a compiled virtualenv in the JAR won't incur that much overhead:
download all dependency packages into the tmpdir
Build a virtualenv and install the dependencies from disk so pyleus can run --describe on each component
Include the sdists/whls instead of the virtualenv in the JAR
Before starting up, build a virtualenv from the included sdists/whls
There is a class of known problems with moving around virtualenvs, not the least of which is that it doesn't work if the same python version isn't installed in the same place between the build machine and Storm machine.
It is possible that doing the following instead of including a compiled virtualenv in the JAR won't incur that much overhead:
--describeon each component