On Mon, Apr 9, 2012 at 11:03 PM, Joachim Durchholz <[email protected]> wrote: > Am 10.04.2012 05:31, schrieb Aaron Meurer: > >> So I think we should >> just fix issue 2899, and even if there are other recursion problems >> they shouldn't show up (unless we are very unlucky). We need to fix >> that issue anyway. > > > As far as I understand the situation, we have an infinite recursion on the > SymPy side, which also crashes the Python side of things. > > So we need to fix the recursion anyway.
Yes, this is right. The test is an XFAIL test, so it's just testing the broken behavior. But we should fix it. > Python crashing means we get a stack dump and all tests further down the > line get ignored. So the consequence is that some recursion bugs (which need > to be fixed anyway) need a higher priority than they would have gotten > otherwise, is it? >From my understanding, some C Python function was suppressing the error, which usually is a more subtle bug, but in this case it prevented it from stopping the Python stack from overflowing. I think the chances of hitting this particular bug are pretty slim. You have to call whatever Python function was suppressing the error exactly when the Python stack fills up. That's why my patch made the error show up: it added another function call to the stack, making the error show up in a different place. Also, if it were easy to hit, someone else would have found it by now. Aaron Meurer -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
