[New-bugs-announce] [issue38869] Unexpectedly variable result
Ian Carr-de Avelon
report at bugs.python.org
Wed Nov 20 16:32:48 EST 2019
New submission from Ian Carr-de Avelon <carrdeavelon at gmail.com>:
I can't understand why the result of changes() in the example file changes. I get:
[[6.90642211e-310]
[1.01702662e-316]
[1.58101007e-322]]
[[0.]
[0.]
[0.]]
with an Ubuntu 14 system that has had a lot of changes made. I've checked the same happens on pythonanywhere.com so it does not seem to just be my system is broken. I wondered if there was some strange state in cv2 I don't know about, but as commenting out the tvec=np.zeros(3) line removes the behaviour I think there is something strange here. Now I've got it down to a few lines I can find a work around and obviously numpy and opencv are huge packages and it may be in their court, but I think it is worth someone taking a look who knows more than me.
Yours
Ian
----------
files: bug.py
messages: 357105
nosy: IanCarr
priority: normal
severity: normal
status: open
title: Unexpectedly variable result
type: behavior
versions: Python 2.7
Added file: https://bugs.python.org/file48727/bug.py
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38869>
_______________________________________
More information about the New-bugs-announce
mailing list