-
-
Notifications
You must be signed in to change notification settings - Fork 533
Null generated environment settings #418
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
Comments
Note: This suggestion is incorrect. Keeping it here for the conversation history. I had the same desire and I found a way, thought it maybe leveraging an unintentional feature...
This is (unfortunatly) on windows using tox 2.4.1 |
That would actually be cool, but it doesn't work for me. Note that I'm using tox 2.5.0 on Linux.
Note that @hpk42 The empty |
oh you're right. |
So a workaround that does work...
Basically explicitly create sections for the "normal" runs and specify the command there in each run. This could be made more maintainable by utilizing section substitutions, https://tox.readthedocs.io/en/latest/config.html#substitution-for-values-from-other-sections I did a dump of |
@speedyleion Thanks, that does work, but it's less convenient the more factors are involved. E.g. I have three dimensions of factors, the Python version (3.4, 3.5, and 3.6), the coverage type (no-coverage, coverage, diff_cover), and the database type (sqlite, mysql, pg). I still kind of like the empty |
I agree, it would be nice to have a way to specify project defaults, without forcing a default factor. Talking with a colleague we were thinking another idea is to put them in the [tox] group.
|
I was thinking about this last night and I realized that a solution to #238 could also solve this problem. If you combine the idea of groups and aliases, then it might not matter that you don't have null environments because you can hide the less convenient
Now I could do the following:
This gives me my succinct cli invocation, which is the real motivation behind the request for null environments. It means that I don't need null environments in my |
closing in favour of #238 |
I could have sworn I reported this before, but I can't find it. Maybe I only mentioned it on the mailing list, or described it differently on the old Bitbucket tracker. Anyway...
Let's say I want the following environments:
Currently I have to specify them like this:
And I have to run a "no coverage Python 3.5" test like this:
tox -e py35-nocov
But what I'd really like to do is to say
tox -e py35
for the "no coverage" case. However I can't do this:because the first command, i.e.
python -m nose2 -v {posargs}
will run for every test environment, which is definitely not what I want. I need a way to run commands when they don't match a generated environment. Perhaps something like this would do the trick?It's possible of course that I'm missing something obvious.
The text was updated successfully, but these errors were encountered: