Use logging instead of printing
- Dominant language
- Python
- Stars
- 59
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
Heyo! I'm wondering if instead of having a bunch of print statements (that the user cannot control)
```
Retrieving repository info for LLNL/b-mpi3
Checking GitHub API token... Token validated.
Auto-retry limit for requests set to 10.
Reading '/home/vanessa/Desktop/Code/contributor-ci/contributor_ci/main/extractors/repos/repos-info.gql' ... File read!
Sending GraphQL query...
Checking response...
HTTP STATUS 200 OK
API Status {"limit": 5000, "remaining": 4998, "reset": 1624819230}
Data received!
```
It would be possible and make sense to using logging instead, so it can be made quiet? For my user case, I have a command that hits a few API endpoints and then needs to pipe to file, and I'm not able to control this output.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Python entry points that emit the listed status messages and inspect the referenced contributor_ci/main/extractors/repos/repos-info.gql flow. Confirm how command output is currently mixed with API activity, then verify that users can control diagnostic output while piping command results without extra messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100