ivanhercaz / ivanhercaz/CanaryBot
Replace print functions by logging system
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Prints are not the best way to show in the terminal what is doing the script, neither it is the best way to test if something works as expected. These prints aren't necessary due it is possible to address its purposes with:
- Show information about what is doing the script: logging system (`log.py`).
- Test how is working an executed piece of code: [PySnooper](https://github.com/cool-RR/PySnooper)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading log.py and locating the script's print calls; the issue does not identify specific source files or tests. Audit each print's purpose and replace status output with the logging system, with no unnecessary print-based reporting remaining; PySnooper is suggested for inspecting execution rather than testing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100