Typo in numpy types conversion breaks contour functions in Python (Patch #2611)

Added by Tristan VINCENT over 12 years ago. Updated about 12 years ago.

Status:	Done	Start date:	2012-12-07
Priority:	High	Due date:
Assignee:	Vadim Pisarevsky	% Done:	90%
Category:	python bindings
Target version:	2.4.4
Affected version:	2.4.3	Operating System:
Difficulty:		HW Platform:
Pull request:

Description

There is a typo in cv2.cpp for the numpy integer type, which breaks some of the contour functions Python bindings (but maybe other functions as well).

The bug apparently exists in 2.4.3 release, as mentionned here

Attached is a patch that corrects the problem.

Corrected-typo-in-numpy-data-type.patch (1.3 kB) Tristan VINCENT, 2012-12-07 03:13 pm

Associated revisions

Revision cd46a674
Added by Vadim Pisarevsky about 12 years ago

applied patch #2611 that also likely fixes #2505

Revision a519bbc6
Added by Vadim Pisarevsky about 12 years ago

Extended python bindings to support scalar values and tuples in place of InputArray (i.e. Mat) - ticket #2658. Added tests for #2611, #2505, #2658

Revision 2320ec76
Added by Vadim Pisarevsky about 12 years ago

Extended python bindings to support scalar values and tuples in place of InputArray (i.e. Mat) - ticket #2658. Added tests for #2611, #2505, #2658

History

#1
Updated by Anna Kogan over 12 years ago

Hello Tristan!

Thank you for reporting the issue and especially for your patch!
If it's possible, could you please make a pull request for it there: http://opencv.org/opencv-pull-requests-test-results.html ? It would be highly appreciated!