> > $ apt-get install sage > > $ python > > Python 2.5.1 (r251:54863, Aug 17 2007, 00:51:07) > > [GCC 4.1.3 20070812 (prerelease) (Debian 4.1.2-15)] on linux2 > > Type "help", "copyright", "credits" or "license" for more information. > > >>> from sage.all import * > > >>> print x**2 > > > > And I could use anything that SAGE wraps. Everything under one hood. Period. > > Indeed! This will be even better in the direction I like. The key > thing you (=Ondrej) > want really is that it is all under *your* existing roof (i.e., Debian) too.
Yes, that's true that all I really care about is Debian on my computers. But fortunately by the spirit of Debian, if it works nicely in there, it's (usually) not a big problem to get it work elsewhere, the same nicely. > I did a sage -upgrade and am waiting for it to finish building... > When that finishes I'm going to check out your segfault with Spec(QQ) > == 5. (If it doesn't finish soon I'll be on my way to campus, but > will get back to you tonight at the latest) This should not segfault, > but if it does I think it is due to an error elsewhere. Also, I think > we should only be callling _sage_ if one of the objects is not a > SageObject, rather than if one of the objects is not an Element. The > requirement would be that _sage_ MUST return an instance of > SageObject to avoid infinite recursion. > > I still think _verify_canonical_coercion_c is the wrong thing to use > here, there is no reason that x._sage_() and y._sage_() should have > the same parent (e.g. one could be an element of SR, the other a sage > Integer), and at this point we should be able to succeed even if they > don't have the same parent by (re-)calling the Sage coercion model on > the Sage elements. Yes, I also think it's a bug somewhere else in SAGE. If you are able to figure it out, I am curious about it. Try my first patch, that will segfault. My second patch passes fine. Ondrej --~--~---------~--~----~------------~-------~--~----~ 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/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
