Closed GijsTimmers closed 8 years ago
implemented basic idea, linked above; added --debug
option (toggled on by default in kotnetcli_test.py
)
Exactly. Nice job!
note: whereas logging of setup-errors (eg import failed or so) is fine, we should better not use the logging system to provide users with login-procedure (i.e. worker
) errors (as I did in the above commits)
Instead, we should think about changing the communicator API with error feedback methods
Yes, just use the communicator for expected errors, and use the logging module for more detail on what's happening.
Yes, just use the communicator for expected errors, and use the logging module for more detail on what's happening.
Done #106
Debug stuff like
ik wil bellen blazen
should be elegantly logged using the python logging module.We will work on this when kotnetcli 2.0.0 is released.