Replace prints with logging module
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
Search the repository for print calls first; the issue names no files or tests. Review each call's intended error or info stream, then verify that all replacements use the logging module with errors on stderr and info on stdout.
Written by the indexing model from the issue text.
Description
We should be logging errors to stderr and info to stdout. Let's replace all prints with appropriate use of the logging module. Upstream this'll help nextline, which handles the two streams differently.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 17h 32m
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from simonsobs/sorunlib
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in simonsobs/sorunlib
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100