Obviously, this still uses OpenCV, and that's not going anywhere.
However, removing the python dependency on opencv-contrib-python-headless allows the package to be used with a system version of OpenCV, which likely has better compiler optimisations for the hardware.
It would also mean viewer.py could be removed, and replaced with the native OpenCV implementation, which would be nice.
I think we should move the python OpenCV bindings to extras, such that zoloto[opencv] andzoloto[opencv-headless]` work.
For ease of use, we'd likely need to revert (and modify the implementation of) 940d26a10ed8f9743cc10c64774c8ab8e43c4c34 to defend certain implementations.
Obviously, this still uses OpenCV, and that's not going anywhere.
However, removing the python dependency on
opencv-contrib-python-headlessallows the package to be used with a system version of OpenCV, which likely has better compiler optimisations for the hardware.It would also mean
viewer.pycould be removed, and replaced with the native OpenCV implementation, which would be nice.I think we should move the python OpenCV bindings to extras, such that
zoloto[opencv] andzoloto[opencv-headless]` work.For ease of use, we'd likely need to revert (and modify the implementation of) 940d26a10ed8f9743cc10c64774c8ab8e43c4c34 to defend certain implementations.