-
-
Notifications
You must be signed in to change notification settings - Fork 512
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
allow tox to reject invalid or unexpected target parameters #646
Labels
Comments
I get
with nothing being created on tox 2.8.0 and 2.9.1. This looks like your expected behaviour? |
@cryvate this sounds like good news to me. No more typos in environment name! A good reason to bump tox. |
@ssbarnea: it seems that this was added/changed in version 1.8.1. I think this can be closed. |
Assuming this is fixed then! FWIW this has been the behaviour for as long as I can remember using tox 😉 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Currently tox will try to create any unexpected target environment even if the user makes a typo. We would like to be able to have an option that will make tox return an error on unknown environments.
Because this may break some setups I suspect that the correct implementation would be to add add a tox.ini config item that would enable this behaviour, like
enforce_envlist=True
Expected behaviour
The text was updated successfully, but these errors were encountered: