You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FindPython3 was introduced in CMake 3.12 and OpenCV's cmake_minimum_required is 3.5(3.1). So, should we keep both old FindPythonInterp and FindPythonLibs and new FindPython3?
Currently, OpenCV has both Python2 and Python3 bindings. However, Python2 reached end of life on January 1, 2020 and you only mentioned FindPython3. Should we still keep Python2 binding?
Looks like, yes. We have to support both branches for now. The team investigates an option to raise minimum CMake version, but for 5.x for now.
Python2 is not supported by OpenCV team any more. We do not test it regularly and do not produce opencv-python packages. So, I think we can safely drop Python2 support with latest CMake.
System Information
Details: https://cmake.org/cmake/help/latest/policy/CMP0148.html
Related Patch: #25585
Detailed description
Current approach was deprecated with CMake
Steps to reproduce
Issue submission checklist
The text was updated successfully, but these errors were encountered: