posit-dev / posit-dev/py-shiny
Error messages should go to stderr, not stdout
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.8k
- Forks
- 135
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 21
Description
(via @ChandlerTayek on #305)
A lot of our logs are lazy prints right now, they really should be going to stderr, probably using proper logging (like the messages from uvicorn use).
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No files or tests are identified. Start by locating the lazy print calls that produce logs and review how uvicorn emits messages; determine the project-wide scope and expected logging approach before changing anything. Done means the relevant logs consistently go to stderr through the chosen logging mechanism.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100