I reported this here:
http://www.sagemath.org:9002/sage_trac/ticket/328
I then fixed it for sage-2.4. The fixed involved re-enabling killing of
maxima variables when the corresponding SAGE object
goes out of scope.
On 3/10/07, Gregory Vanuxem <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> Here is a simple session that exhibits a bug, I don't know "where" it
> comes from:
>
>
> ========================================================================
> $ sage
> ----------------------------------------------------------------------
> | SAGE Version 2.3, Release Date: 2007-03-06 |
> | Type notebook() for the GUI, and license() for information. |
> ----------------------------------------------------------------------
>
>
> sage: f = maxima.function('x','gamma(x)')
>
> sage: # f # do not print f
>
> sage: g = f(1/7)
>
> sage: g
> gamma(1/7)
>
> sage: f = gp(sin(x))
>
> sage: f
> x - 1/6*x^3 + 1/120*x^5 - 1/5040*x^7 + 1/362880*x^9 - 1/39916800*x^11 +
> 1/6227020800*x^13 - 1/1307674368000*x^15 + O(x^17)
>
> sage: maxima(sin(x))
> gamma(x)
> ==========================================================================
>
>
> At the end maxima(sin(x)) returns the MaximaElement gamma(x) :-(
>
> I spent some time trying to find a simple and reproducible way that
> triggers this bug, modifying one line, for example printing 'f', can
> lead to an, apparently, correct computation so try this in a fresh
> session.
>
> Many thanks for your work,
>
> Greg
>
>
>
> >
>
--
William Stein
Associate Professor of Mathematics
University of Washington
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
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/
-~----------~----~----~----~------~----~------~--~---
