Bruno Oliveira

Yeah that color coding of the status is hard coded in `terminal.py`, without a chance for hooks to customize it. One solution would be to extend `pytest_report_teststatus` so it can...

I'm OK with implementing the change I outlined above (the `Union` with 3-tuple and a new small attrs class), but let's ask other maintainers if they find it a good...

> as much as rich seems really cool I think it's a little unstable at the moment and a fairly heft dependency to pull in Same thoughts here: really cool...

Oh I'm sorry, I misunderstood the issue: `pytest_report_teststatus` already supports returning an optional styling: ```python @hookspec(firstresult=True) def pytest_report_teststatus( report: Union["CollectReport", "TestReport"], config: "Config" ) -> Tuple[str, str, Union[str, Mapping[str, bool]]]:...

> Would that approach also address the lack of coloring in the === short test summary info === section? This has actually been fixed by #9875 and will be available...

That's indeed an interesting idea! > perhaps don't show decorators at all I don't think that's a good idea: at work we have decorators which are important to understand a...

Hi everyone, What I believe is happening is: 1. pytest changes `sys.stdout` and `sys.stderr` to a buffer while importing test modules. 2. If there's user code setting up logging and/or...

After reading this thread and considering this some more, I think the real issue is that pytest is not playing well with *any* system which hijacks `sys.stdout` or `sys.stderr`, and...

@RonnyPfannschmidt gentle ping. 👍

> note, this should be a opt in via config, potentially by naming a policy, as dropping everything passed by default changes the debug-ability when one wants to compare passed...