trying to be backward compatible

[ghost]

No description provided.

[ghost]

I'm not sure though if we shouldn't first check for cv2 instead of cv but also I don't know if there is an older cv2 which was working with the older engine.py but now with the newer opencv engine it doesn't work anymore?! (Also is travis using opencv2 or opencv3?)

[ghost]

I see that there is really an cv2 for opencv2 .. so unsure how to handle that really

[ghost]

tested now, opencv2.4 works with the engine_cv3 without a glitch.. so if I recall this, I would probably remove the engine.py and replace it with the engine_cv3.py or is there still a need for the old cv C interface?

[ghost]

2.3 beta

June, 2011

* python
Now there are 2 extension modules: cv and cv2. cv2 includes wrappers for OpenCV 2.x functionality. opencv/samples/python2 contain a few samples demonstrating cv2 in use.

so I think it is quiet okay to say, that we don't want to keep cv anymore, right?

[christianjgreen]

The cv interface (C api) was officially deprecated about two years ago. It would be best to be compliant and remove the old engine.

[christianjgreen]

Have you been able to get a working travis build with it?

[christianjgreen]

I believe I found a working pre-compiled package. I'll be using https://github.com/skvark/opencv-python for testing.

[ghost]

yeah the opencv-python thing is what I use as well, but this will always have the latest OpenCV version built-in .. so if you want to test for OpenCV 2.4 or any other in OpenCV 3.x except the latest stable, it won't really help.. so it depends what you think you want to achieve with the testing