-
-
Notifications
You must be signed in to change notification settings - Fork 529
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
{envtmpdir} not created by default, unless already present #399
Comments
I agree solution 1 seems to be the correct one. The documentation reads:
So I would expect it to be available (and empty) for the commands to use. |
I agree -- we should create the tmpdir if it's not there. Fancy a PR? There's soon going to be the tox-2.5 release (maybe mid/end next week) btw :) |
…t clearing it if it already existed. Fixes issue tox-dev#399.
…t clearing it if it already existed. Fixes issue tox-dev#399.
fixed by @manuljacob's PR. Thanks! |
{envtmpdir}
is not created by default. However if it's already present, it's deleted and recreated. This behavior is possibly confusing.An example:
I see two solutions to provide a consistent environment on each test run.
Solution 1 would be more convenient, as it saves the user from manually adding a command to every testenv to create the directory. However a configuration using the
recreate
option could rely on that the envtmpdir never exists when run.The text was updated successfully, but these errors were encountered: