Use Python logging framework
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.4k
- Forks
- 1k
- Avg merge
- 22h 17m
- Merged PRs (30d)
- 3
Description
At the moment, all output from opencv-python C++ components seems to be emitted directly like this:
[ WARN:0@10009,161] global qrcode.cpp:2913 decodingProcess QR: ECI is not supported properly
This does not align nicely with the regular Python logging. It would be great to let opencv-python use the proper logging capabilities of the current environment instead.
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.
Research direction
The issue names no files, tests, or entry points. Start by reproducing the direct C++ output from opencv-python and tracing how it reaches the Python environment; done means OpenCV component messages use the environment's regular Python logging capabilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100