Meh. Just create a stdout module that proxies calls to stderr (or vice versa) and then just make a config thing at the top. Should be as simple as I first thought that way.
On Tue, Aug 9, 2016 at 4:22 PM, Paul Davis <[email protected]> wrote: > New logging also doesn't actually have stdout as an option but that'd > be a trivial change to make. Though the name of the writer could be > weird. > > On Tue, Aug 9, 2016 at 4:06 PM, Alexander Shorin <[email protected]> wrote: >> On Tue, Aug 9, 2016 at 10:00 PM, Jan Lehnardt <[email protected]> wrote: >>> I'd say we keep 1.x behaviour of logging to file by default with an option >>> to override to stdX for the envs that want that. >> >> Actually, 1.x behaviour is about to log both to stdout/stderr and file >> at the same time. Package maintainers actually just suppress >> stdout/stderr because we already have a file logging. Those options -o >> and -e about to redirect stdout/stderr to specific files, but this >> doesn't overrides file logging. >> >> -- >> ,,,^..^,,,
