The writeReg function in the python API makes what I feel are undesired print statements to terminal. I would suggest that this is changed to only make print statements when a debugging flag was provided.
Types of issue
[ ] Bug report (report an issue with the code)
[x] Feature request (request for change which adds functionality)
Expected Behavior
The code would only print the write attempt to terminal if a debug flag existed and debug=True was passed at runtime.
Brief summary of issue
The
writeReg
function in the python API makes what I feel are undesired print statements to terminal. I would suggest that this is changed to only make print statements when a debugging flag was provided.Types of issue
Expected Behavior
The code would only print the write attempt to terminal if a debug flag existed and
debug=True
was passed at runtime.e.g.
Changing the function declaration from:
https://github.com/cms-gem-daq-project/reg_utils/blob/2879f89d67994212d0d71f0616224195edc79ea9/python/reg_interface/common/reg_base_ops.py#L99
to:
And changing line 104:
https://github.com/cms-gem-daq-project/reg_utils/blob/2879f89d67994212d0d71f0616224195edc79ea9/python/reg_interface/common/reg_base_ops.py#L103-L104
to:
Current Behavior
Shown in lines 99-128:
https://github.com/cms-gem-daq-project/reg_utils/blob/2879f89d67994212d0d71f0616224195edc79ea9/python/reg_interface/common/reg_base_ops.py#L99-L128
Presently the code will always print the write attempt to terminal.
Context (for feature requests)
Clutters terminal output when write transactions are performed, e.g.:
Your Environment