[TIP] [tox] Capturing output from commands
andre.l.caron at gmail.com
Mon Jun 13 13:14:20 PDT 2016
Thanks, I'll take a crack at that!
I hadn't noticed before, but by fiddling around a bit, but it looks like:
- Tox merges stdout and stderr of the commands into Tox's stdout.
- shell redirection inside the commands doesn't work (at least on Windows).
Intuitively, I would expect stderr from my commands to be forwarded to
stderr. Since this is not the case, I was willing to fall back onto
redirecting stdout from my process directly to a file, but then I can't do
that inside my Tox.ini file as my command gets the ">foo.log" as a CLI
Is there any non-obvious rationale for this? If not, would you consider
changes in this behavior?
On Mon, Jun 13, 2016 at 12:54 PM, Florian Bruhin <me at the-compiler.org>
> Hey André,
> * André Caron <andre.l.caron at gmail.com> [2016-06-13 12:07:37 -0400]:
> > I looked through Tox' docs and CLI help, but I can't find a "silent" mode
> > or a way to force (only) Tox to write to stderr.
> > Do you have anything to recommend? If not, any chance you would
> consider a
> > patch to introduce a silent mode or a config change to send Tox' logs to
> > stederr?
> There's an issue for a -q flag, but nobody worked on it so far:
> I still want to work on that, but never got to it with all the other
> FOSS stuff I do :) So if you want to work on a patch, please do!
> http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
> GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
> I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the testing-in-python