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

Make tox fail on unspecified pyXX environments #1657

Closed
chrisjsewell opened this issue Aug 21, 2020 · 1 comment
Closed

Make tox fail on unspecified pyXX environments #1657

chrisjsewell opened this issue Aug 21, 2020 · 1 comment

Comments

@chrisjsewell
Copy link

When submitting a bug make sure you can reproduce it via tox -rvv and attach the output of that to the bug. Ideally, you should also submit a project that allows easily reproducing the bug. Thanks!

tox will fail on a "completely" unknown environment (as fixed in #1160).
However, if I have an environment list like:

$ tox -a
py36-sphinx2
py36-sphinx3

running tox -e py36 will still run and create an environment.

Is there a way to stop this?

@chrisjsewell chrisjsewell added the bug:normal affects many people or has quite an impact label Aug 21, 2020
@gaborbernat gaborbernat removed the bug:normal affects many people or has quite an impact label Aug 21, 2020
@gaborbernat
Copy link
Member

There's no way to stop it and that's on purpose. It offers the flexibility to test pythons that are not defined within your tox.ini.

@tox-dev tox-dev locked and limited conversation to collaborators Jan 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants