Use Python logging framework

[stefan6419846]

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.

[jadhavroshani713-sys]

Thanks for explaining this. I’m new to OpenCV-Python and noticed these warning messages too. Is there currently any recommended way to redirect them into Python’s logging framework?

[Sedhubabu]

Currently, OpenCV’s C++ backend prints warning messages directly to the console instead of using Python’s logging system.
Because of that, the logs do not follow our application's logging format and cannot be controlled using our logging configuration.

To make logging consistent and manageable, we can set the OpenCV log level (for example, to ERROR or SILENT) using environment variables or cv2.utils.logging.setLogLevel().