Skip to content
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

Should tox -e unknown output to stderr? #1434

Closed
dmtucker opened this issue Oct 12, 2019 · 3 comments
Closed

Should tox -e unknown output to stderr? #1434

dmtucker opened this issue Oct 12, 2019 · 3 comments
Labels
feature:new something does not exist yet, but should

Comments

@dmtucker
Copy link

$ tox -e foo
ERROR: unknown environment 'foo'

These seem inconsistent:

$ tox -e foo >/dev/null
$ tox -c foo >/dev/null
ERROR: foo is neither file or directory
ERROR: tox config file (either pyproject.toml, tox.ini, setup.cfg) not found

Is this intentional?

@gaborbernat
Copy link
Member

I agree with your proposal, could be part of #1394 as it would be breaking.

@gaborbernat gaborbernat added the feature:new something does not exist yet, but should label Oct 14, 2019
@gaborbernat
Copy link
Member

Feel free to open a PR against master and fix it. My available efforts at the moment are aimed at fixing this as part of #1394, but that probably will take a while (ETA September).

@gaborbernat
Copy link
Member

Actually, in tox 4 we allowed users to create new environments on the fly, so in the above case the error message is no longer displayed and instead we run the foo environment as it would be defined under envlist

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature:new something does not exist yet, but should
Projects
None yet
Development

No branches or pull requests

2 participants