# Sympy integration algorithm towards -infinity

 1 Following achrzesz hint about integral's algorithm option, I tried (Sage 4.7.2): integral(1/x^2, x, -infinity, -1, algorithm='sympy') Unfortunately, I got: Traceback (click to the left of this block for traceback) ... AttributeError: 'MinusInfinity' object has no attribute '_sympy_' What's going wrong? asked Jan 21 '12 Green diod 63 ● 2 ● 5 ● 12 tmonteil 3573 ● 3 ● 37 ● 83 http://wiki.sagemath.org/... 1The workarounds are good for now. I've opened the auspicious ticket # 12345 (http://trac.sagemath.org/sage_trac/ticket/12345) for the underlying issue.kcrisman (Jan 23 '12)

 1 It seems to be a bug. sympy can recognize infinity but not minus infinity of sage. You can try to directly call sympy integrate instead import sympy as sp a=sp.Symbol('a') b=sp.integrate(1/x^2,(x,a,-1))._sage_() b.substitute(a=-oo) posted Jan 21 '12 Shashank 1720 ● 8 ● 30 ● 62 How do you get this infinity symbol? But most importantly, do you input this code in a simple python interpreter or in Sage? What is this _sage_() method?Green diod (Jan 23 '12)How do you get this infinity symbol?Green diod (Jan 23 '12)Every element from another program (such as sympy) has a _sage_ method to convert its things back to Sage objects. The infinity symbol is just one of the several ways to represent infinity in Sage (and several other programs of this type); in principle, it should be equivalent to using infinity, but apparently this bug leaves it to not work for Sympy.kcrisman (Jan 23 '12)All right, but how do you input the infinity symbol?Green diod (Jan 23 '12)1-oo is just minus oo the alphabetsShashank (Jan 23 '12) see 1 more comment
 1 sage: from sympy import * sage: integrate(1/x^2, (x, -oo, -1), algorithm='sympy') 1 posted Jan 21 '12 achrzesz 1691 ● 4 ● 16 ● 38 How do you get this infinity symbol?? Anyway, I still get the same error even at the console using -infinityGreen diod (Jan 23 '12)
 0 This works as of Sage 5.1 (see trac #12345). (Please tell me if old questions shouldn't be necromanced; I just add answers for future reference to questions where the issue has been fixed.) posted Jun 05 Eviatar Bach 653 ● 4 ● 22 ● 34 1Seems fine to me! Or you could have commented under where I mentioned the ticket first, either is fine. Having complete info is good. Maybe we should close questions like that...kcrisman (Jun 05)1I am not sure we should close such questions, or at least we should'nt delete them, since trac points to them, and we should keep examples, even if they are fixed. That said, it could be nice to have a better integration between ask and trac, as well as a system of 'categories' that allow to separate questions related to a sage bug or questions related to a failed build, or questions related to how to use sage (probably the most interesting for the readers). I am currently trying to do this via tags (removing bug tag where this is not a bug, and adding confirmed_bug or fixed_bug tag when this is a bug), but it is quite a long task, and having an automated link between ask and trac could be of great help.tmonteil (Jun 06)No, we shouldn't delete them; closing just means it's been resolved, I would say. But it's not really that important.kcrisman (Jun 06)

[hide preview]