Use Python logging framework

Open
#1,208 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp, python
Domain
developer-experience

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.

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.

Dominant language
Python
Stars
5.4k
Forks
1k
Avg merge
22h 17m
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from opencv/opencv-python

All issues in opencv/opencv-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.