-
We rely solely on __debugbreak(), MSVC's debugger and printf() to get the job done.
This is bad. It must be addressed.
-
There are certain cases where it might be nice to warn with a logger (e.g. network ambiguity during decoding). Is using the `logging` module consistent with design goals here?
-
ATM (v1.8.3-10-g4a2e6f7a) logging facilities are primarily used by invoking `logging.` instead of a dedicated logger:
```shell
❯ git grep 'logging\.\(info\|error\|debug\|warning\)' | wc -l
122
❯…
-
We should add logging to help with debugging. Since error handling is non-existent, this has even higher importance than usual. Thanks to Leo Broska for the suggestion.
-
Log the shit out of everything. EVERYTHING.
-
In order to better understand the internal flow when debugging or developing, it would be very helpful to have run-time switchable logging, including debugging and tracing levels.
For a simple and …
-
Submitted by: tectsoft (tectsoft)
Votes: 4
SFID: 1108199#⁠
Submitted By: tectsoft
Would be nice to have improved logging facilities\.
\- Log failed connections\. \(see request 1107907 as we…
-
Currently `salt/log` package tries to abstract Logrus and Zap into a common formatted-logger interface (i.e., `Infof(msg string, args ...any)`, etc. ). While `logrus` is designed as a formatted-logger…
-
-
I'm looking into migrating an existing project from Python's built-in `logging` facilities to `loguru`. The code base uses printf-style formatting quite extensively, e.g.
```
logger.info("Loading …