Logging is currently done via print and verbosity flag variables. This is unnecessary code overhead since there are built in logging solutions available in python. Suggestion would be to use the logging module. This also provides the establishment of different handlers to the same logger. Thus it is possible to write the log to a file and to the LogWidget or onto the console with full control over the verbosity.
Logging is currently done via `print` and `verbosity` flag variables. This is unnecessary code overhead since there are built in logging solutions available in python. Suggestion would be to use the `logging` module. This also provides the establishment of different handlers to the same logger. Thus it is possible to write the log to a file and to the LogWidget or onto the console with full control over the verbosity.
open individual issues -> board decision on the way forward
TODO:
- [ ] add global logging concept for `pylot`
- [ ] add handler to log to the widget
- [ ] log level as an option
- [ ] add handler to log to a file
- [ ] log level always `debug`
- [ ] add handler to log to `stderr`
- [ ] log level `error`
- [ ] add handler to log to `stdout`
- [ ] log level `warning`
- [ ] identify usage of `verbosity` and `print` statements
- [ ] open individual issues -> board decision on the way forward
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Logging is currently done via
printandverbosityflag variables. This is unnecessary code overhead since there are built in logging solutions available in python. Suggestion would be to use theloggingmodule. This also provides the establishment of different handlers to the same logger. Thus it is possible to write the log to a file and to the LogWidget or onto the console with full control over the verbosity.TODO:
pylotdebugstderrerrorstdoutwarningverbosityandprintstatements