Please do not use logging basicConfig for library software
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 129
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I am developing a larger public software which uses gtfparse as a component (Thank you, it has been proving very helpful)
I note in gtfparse/read_gtf.py , there is a call of logging.basicConfig ; This call basically overwrites the logging config of my software (and any other users who may be using logging as part of their softwares)
It would be good in a future version if you were to remove this call, so that I don't need to manually monkey patch basicConfig out in my software.
Thank you!
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
Start in gtfparse/read_gtf.py and inspect the logging.basicConfig call and its surrounding logging setup. Confirm how the library configures logging, then verify that the library no longer overrides an embedding application's logging configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- bioinformatics
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100