Hi Jeroen, First of all: Thank you for tracking it down!
On 24 Mai, 09:52, Jeroen Demeyer <[email protected]> wrote: > On 2011-05-23 18:14, Jeroen Demeyer wrote: > > static void > __pyx_tp_dealloc_4sage_5rings_10polynomial_21polynomial_zmod_flint_Polynomial_template(PyObject > *o) { > { > PyObject *etype, *eval, *etb; > PyErr_Fetch(&etype, &eval, &etb); > ++Py_REFCNT(o); > > __pyx_pf_4sage_5rings_10polynomial_21polynomial_zmod_flint_19Polynomial_template_3__dealloc__(o); > if (PyErr_Occurred()) PyErr_WriteUnraisable(o); > --Py_REFCNT(o); > PyErr_Restore(etype, eval, etb); > } > > __pyx_ptype_4sage_5rings_10polynomial_18polynomial_element_Polynomial->tp_dealloc(o); > > } > > The problem is the line > if (PyErr_Occurred()) PyErr_WriteUnraisable(o); > > Since this code is generated by Cython, perhaps it is not possible to > solve this problem without patching Cython. It says something about dealloc. That sounds to me as if the error is raised in sage.rings.polynomial.polynomial_template.Polynomial_template.__dealloc__ Raising an error in dealloc should be avoided, shouldn't it? Cheers, Simon -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
