common-workflow-language / common-workflow-language/cwltool
refactor logging?
Open
enhancement
- Dominant language
- Python
- Stars
- 376
- Forks
- 255
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 12
Description
We currently use a single logger `cwltool` instead of a module name based approach. Also the logging is always turned on instead of only when `cwltool.main.main()` is called
Contributor guide
Research direction
Start at cwltool.main.main() and trace where the single `cwltool` logger is configured and used across the package. Check how logging behaves when modules are imported versus when `main()` is called. Done means module-based loggers are used and logging is enabled only through `cwltool.main.main()`.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100