On Feb 24, 8:52 pm, Robert Miller <rlmills...@gmail.com> wrote: > I'm working on wrapping a C package in Cython for use in Sage, and I'm > having some trouble. I think the problem has to do with the fact that > the C program uses stderr to report issues. When the program exits, I > get the following message: > > SystemError: error return without exception set
I doubt that sending something or not sending something to stderr is going to make any difference. It's just a writable stream. My guess is that a routine that is expected to return a PyObject* is returning NULL. This signals the occurrence of an error in Python and I can imagine that when the appropriate exception reporting fields are not set up when this happens, this is what one would expect. I imagine this could happen if cython thinks a routine returns a PyObject * (i.e., object -- the default type in cython), but the routine in reality returns an integer 0. A mistranslated ".h" file could easily cause this. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
