This forum is disabled, please visit https://forum.opencv.org
 | 1 | initial version |
import cv2.cv as cv is absolutely valid and is favorable to your second variant (since with your second variant you wouldn't need to write cv.method() but just method() which might get confusing over time). BUT, really, I'd try to circumvent cv2.cv as much as possible and use the functionality of just the cv2 module (exist there modules at all which are only in cv but not in cv2?).
I don't know, but python3 support will come with OpenCV 3.0 afaik.
| | 2 | No.2 Revision |
import cv2.cv as cv is absolutely valid and is favorable to your second variant (since with your second variant you wouldn't need to write cv.method() but just method() which might get confusing over time). BUT, really, I'd try to circumvent cv2.cv as much as possible and use the functionality of just the cv2 module (exist there modules at all which are only in cv but not in cv2?).
I don't know, but python3 support will come with OpenCV 3.0 afaik.afaik. Maybe cv2.cv will vanish then, too.
