Ronny Pfannschmidt
Ronny Pfannschmidt
unfortunately not, im not familiar with the surrounding libs in use
as far as im understanding, the desire here is to either take the color of the verbose word, or the symbol and apply it to the status line i would...
i want to weight in, that we ideally avoid propagating the terminal-writer styling apis any more than they are already in by accident, i really would like to see something...
im not proposing to replace coloring with rich anytime soon (in fact - if ever i would like to see a official pytest-rich/pytest-textual plugin in future that enables more fancy...
@nicoddemus what i want to propose is that we take the color, that we support for the verbose name/name anyway - and also use it for the unknown statuses currently:...
@nicoddemus bascially i want to pass the markup that was added in that hook into the status collection as well, that way we can use the color markup we already...
Im on board with the idea, but i would like to investigate a better name for the parameter Indirect is a bit hard to intuitively understand
i'd rather switch thos to a exception that clearly tells to use a better logging setup and a documented best practice for setup of logging from my pov its important...
whats preventing issuing a actual issue against ros? i an case its safe to say that hiding this issue will just make things hideeous and strangely, i would strongly suggest...
@bluenote10 in that case i advise deactivating capture as a starting point and i suspect there can be a pytest plugin, that hijacks the logging system on rhos for example,...