Project

General

Profile

Actions

Feature #2347

closed

Add support for standard logging module

Added by Zach Welch about 9 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
02/24/2015
Due date:
% Done:

90%

Estimated time:
Chirp Version:
daily
Model affected:
(All models)
I read the instructions above:

Description

In order to support a CLI (see issue #2343), the level of output needs to be variable, from terse to verbose. The proper solution will be to use the standard Python logging module. All existing print statements need to be reviewed, as most will need to be converted to use a logging call.

I have patches in hand that get this process started. The first adds a custom logger module and command line options for controlling it from the chirp.py CLI. The second adds all existing debug statements (controlled via CHIRP_DEBUG) to use it. The last converts a handful of other message to use it as well, making the CLI usable.

Additional patches will be required to convert other print statements and to add equivalent option parsing to the GUI.

Actions #1

Updated by Zach Welch about 9 years ago

  • Status changed from New to In Progress
  • % Done changed from 50 to 90

All of the existing print calls have been converted to logging calls. Some may still need to be tweaked (e.g. changed to different logging levels) and more likely need to be added.

Actions #2

Updated by Bernhard Hailer about 4 years ago

  • Status changed from In Progress to Closed

Appears to be complete.

Actions

Also available in: Atom PDF