this will bump wagon to 0.9, which will hopefully be a very short release, and 1.0 will follow soon after
Also, this won't be squashmerged most likely.
don't import virtualenv, only use what virtualenv actually considers its public api (ie. just the executable) (this will make tests pass again)
compat with both virtualenv and the stdlib venv
no shell=true for subprocesses
prefer python -m calls to pip.exe/virtualenv.exe calls because that's easier to keep compatible with linux+windows (and will work with venvs with --no-pip, where pip was installed with editable) (yes, both pip and venv do declare that both ways are supported)
todos for the future, but not in scope for this:
(maybe) replace travis with circle
(maybe) stop using flask in (most?) tests but use a local trivial package instead (needs an index-url instead of pypi)
this will bump wagon to 0.9, which will hopefully be a very short release, and 1.0 will follow soon after Also, this won't be squashmerged most likely.
python -mcalls topip.exe/virtualenv.execalls because that's easier to keep compatible with linux+windows (and will work with venvs with --no-pip, where pip was installed with editable) (yes, both pip and venv do declare that both ways are supported)todos for the future, but not in scope for this: