-
-
Notifications
You must be signed in to change notification settings - Fork 514
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 wildcards to be used in TOXENV and with the -e
option
#318
Comments
Original comment by @eli-collins If it helps, attached is the quick-n-dirty helper script that I've been using to solve a similar problem. Usage is |
Original comment by @eli-collins Instead of a If that were also combined with some flag to make |
Original comment by @edmorley Sorry for the delay in replying. Agree that due to I've also spotted there's a dupe issue #22, albeit there's less discussion there, so might be worth forward-duping. |
Original comment by @hpk42 As far as command line options go i'd rather like a |
Since this issue got moved to git, I'm reuploading the script I've been using, if anyone finds it useful (as code source, or just as is): |
this would be great |
I've created tox-factor, which allows for matching on specific factors. So, instead of
you would run
or
|
Currently it's not possible to use wildcards with TOXENV and/or the
-e
option.For example, I'd like to be able to use:
... to just run the python 2.7 subset of the peep tox config:
https://github.com/erikrose/peep/blob/daa9e87014de1f907fac446f89b9d849665a649e/tox.ini#L8-L9
However since wildcards aren't supported, I've had to resort to a bit of a hack to generate the TOXENV in the Travis config:
See:
https://github.com/edmorley/peep/commit/bb77b96dfd548dd3ba9ac1c595c047dbd3e7f8a9
Many thanks :-)
The text was updated successfully, but these errors were encountered: