Closed hroncok closed 5 years ago
With this, after you run rm -r .tox; tox --print-deps-only
, regular tox
seems to consider the environment created and will try to install dependencies into the current environment.
regular tox seems to consider the environment created and will try to install dependencies into the current environment.
I'll update the "unsupported" check.
I've amended tests and docs, but I think the situation you are describing is not happening. Could you please give full reproducer?
In other words:
After you run rm -r .tox; tox --print-deps-only
, regular tox
aborts with "not supported". At least that is what I believe test_regular_after_first_deps_only_is_not_supported
is checking.
Oh, it aborts after it installs the package :(
Added a test that finds out about this.
Fixed.
Also, in the future, we could simply always delete the fake environment in tox_cleanup
hook and get rid of this restriction, but I'll leave that to another PR.
Opened https://github.com/fedora-python/tox-current-env/issues/14 as a followup.
(Better reviewed commit by commit.)