On 10/09/13 16:48, lcampagn wrote: > This does appear to be a PySide bug. Simple example: > > >>> from PySide.QtGui import QVector3D > >>> class Vector(QVector3D): > ... pass > ... > >>> v1 = Vector(1,2,3) > >>> v2 = QVector3D(1,2,3) > >>> v1+v1 > PySide.QtGui.QVector3D(2.000000, 4.000000, 6.000000) > >>> v2+v2 > PySide.QtGui.QVector3D(2.000000, 4.000000, 6.000000) > >>> v1+v2 > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > RuntimeError: maximum recursion depth exceeded while calling a Python object
Ah I see I was adding two QVector3D when I was trying to make a small testcase. I will submit a bug report to PySide.
> > I have worked around this by converting the QVector3D to a Vector before > adding to self.opts['center']. > Great.
On 10/09/13 16:48, lcampagn wrote: QtGui.QVector3D (2.000000, 4.000000, 6.000000) QtGui.QVector3D (2.000000, 4.000000, 6.000000)
> This does appear to be a PySide bug. Simple example:
>
> >>> from PySide.QtGui import QVector3D
> >>> class Vector(QVector3D):
> ... pass
> ...
> >>> v1 = Vector(1,2,3)
> >>> v2 = QVector3D(1,2,3)
> >>> v1+v1
> PySide.
> >>> v2+v2
> PySide.
> >>> v1+v2
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> RuntimeError: maximum recursion depth exceeded while calling a Python object
Ah I see I was adding two QVector3D when I was trying to make a small
testcase. I will submit a bug report to PySide.
> 'center' ].
> I have worked around this by converting the QVector3D to a Vector before
> adding to self.opts[
>
Great.