marcel/pylot
3
0
Fork 0
Code Issues 7 Pull Requests 1 Releases Wiki Activity

Logging concept #33

New Issue
Open
opened 2023-04-08 07:57:25 +02:00 by sebastianw · 1 comment
sebastianw commented 2023-04-08 07:57:25 +02:00
Collaborator
Copy Link

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.
sebastianw added the
Priority:2
enhancement
 labels 2023-04-08 07:57:25 +02:00
sebastianw added this to the Release v0.3 milestone 2023-04-16 10:30:33 +02:00
sebastianw commented 2023-04-16 10:36:23 +02:00
Author
Collaborator
Copy Link

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
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
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
analysis

   
bug

   
documentation

   
enhancement

   
feature

   
incompatibility

   
management

   
Priority:0

   
Priority:1

   
Priority:2

   
Priority:3
No Label
analysis
bug
documentation
enhancement
feature
incompatibility
management
Priority:0
Priority:1
Priority:2
Priority:3
Milestone
Clear milestone
No items
No Milestone
Release v0.3
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: marcel/pylot#33
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?