Support separate pyvenv for development / build time
The current pyvenv support was primarily built for runtime but it also activated at build time. If we want a particular version of pylint installed at build time, we currently add it to requirements.txt
, which works but has the unfortunate side effect of ballooning the size of the final package
image. We can and should avoid that by supporting a pyvenv for development / build time, ruled by requirements-dev.txt
.
It would be strongly recommended to let requirements-dev.txt
be a superset of requirements.txt
by encouraging inclusion of requirements.txt
from requirements-dev.txt
(that is supported by the format).