Don't print in library
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by locating the library code that prints to stdout and trace how the CLI calls it. Identify which results or status information callers need returned, then check existing tests for library and CLI behavior. Done means library code no longer prints to stdout and the CLI still provides its intended output.
Written by the indexing model from the issue text.
Description
the library part should just do its job (or fail in case of problems), but don't print to stdout as it can not know if such a thing even exists. Instead additional return arguments should be provided. The CLI is not a library.
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- Avg merge
- 10d 34m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 NNPDF/pineko
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Overwrite if encounters stale symlinks to ekosPossibly taken @ashishsoni-ai claimed this 5 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
benchmarks/unit tests
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Check whether IC from theory card is usedMay be free again @kamillaurent claimed this 58 days ago, and no pull request is open. Open
Similar issues
-
opensubtitlescom: provider rejects pt-PT even though its own converter maps itPossibly taken @paulo-0308 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Diaoul/subliminal#1405 ·
-
Internal ErrorOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
frappe/frappe_docker#2071 ·
Maintainers usually reply within 1 day
-
bug python
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
traceloop/openllmetry#4717 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
The-Pocket/PocketFlow#161 ·
-
comp/desktop P2 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#157702 ·
Maintainers usually reply within 1 day