A quick follow-up:
On Nov 19, 2012, at 23:25 , Justin C. Walker wrote:
> On Nov 19, 2012, at 22:36 , Jan Groenewald wrote:
[snip]
> Using Mac OS X, 10.6.8. Sage 4.8 has maxima 5.23 (maxima-5.23.2.p3.spkg);
> 5.0-beta2 has maxima 5.26.
[snip]
>
>> sage: n(jacobi('sn',u+2*I*elliptic_kc(1-m),m))
>
> With sage-5.0-beta2, the above is duplicated, except that the last line has
> been going (and going, and ...) for several minutes now, with no signs of
> abating. It's adding small increments of memory, second by second...
This blew chunks, after a fairly long delay, as follows:
Traceback (most recent call last):
File "<ipython console>", line 1, in <module>
File
"/Users/Sage/sage-5.0.beta2/local/lib/python2.7/site-packages/sage/misc/functional.py",
line 1275, in numerical_approx
return x._numerical_approx(prec)
File "expression.pyx", line 4082, in
sage.symbolic.expression.Expression._numerical_approx
(sage/symbolic/expression.cpp:18084)
File "expression.pyx", line 841, in
sage.symbolic.expression.Expression._convert (sage/symbolic/expression.cpp:5122)
File
"/Users/Sage/sage-5.0.beta2/local/lib/python2.7/site-packages/sage/functions/special.py",
line 510, in _evalf_
return parent(maxima("%s, numer"%self._maxima_init_evaled_(*args)))
File
"/Users/Sage/sage-5.0.beta2/local/lib/python2.7/site-packages/sage/rings/complex_field.py",
line 277, in __call__
return Parent.__call__(self, x)
File "parent.pyx", line 1058, in sage.structure.parent.Parent.__call__
(sage/structure/parent.c:7886)
File "coerce_maps.pyx", line 82, in
sage.structure.coerce_maps.DefaultConvertMap_unique._call_
(sage/structure/coerce_maps.c:3344)
File "coerce_maps.pyx", line 77, in
sage.structure.coerce_maps.DefaultConvertMap_unique._call_
(sage/structure/coerce_maps.c:3247)
File
"/Users/Sage/sage-5.0.beta2/local/lib/python2.7/site-packages/sage/rings/complex_field.py",
line 305, in _element_constructor_
return x._complex_mpfr_field_( self )
File
"/Users/Sage/sage-5.0.beta2/local/lib/python2.7/site-packages/sage/interfaces/maxima_abstract.py",
line 1291, in _complex_mpfr_field_
return C(self._sage_())
File
"/Users/Sage/sage-5.0.beta2/local/lib/python2.7/site-packages/sage/rings/complex_field.py",
line 277, in __call__
return Parent.__call__(self, x)
File "parent.pyx", line 1058, in sage.structure.parent.Parent.__call__
(sage/structure/parent.c:7886)
File "coerce_maps.pyx", line 82, in
sage.structure.coerce_maps.DefaultConvertMap_unique._call_
(sage/structure/coerce_maps.c:3344)
File "coerce_maps.pyx", line 77, in
sage.structure.coerce_maps.DefaultConvertMap_unique._call_
(sage/structure/coerce_maps.c:3247)
File
"/Users/Sage/sage-5.0.beta2/local/lib/python2.7/site-packages/sage/rings/complex_field.py",
line 305, in _element_constructor_
return x._complex_mpfr_field_( self )
File "expression.pyx", line 933, in
sage.symbolic.expression.Expression._complex_mpfr_field_
(sage/symbolic/expression.cpp:5556)
File "expression.pyx", line 792, in
sage.symbolic.expression.Expression._eval_self
(sage/symbolic/expression.cpp:4969)
File
"/Users/Sage/sage-5.0.beta2/local/lib/python2.7/site-packages/sage/functions/special.py",
line 510, in _evalf_
return parent(maxima("%s, numer"%self._maxima_init_evaled_(*args)))
File "lazy_import.pyx", line 199, in
sage.misc.lazy_import.LazyImport.__call__ (sage/misc/lazy_import.c:1509)
File
"/Users/Sage/sage-5.0.beta2/local/lib/python2.7/site-packages/sage/interfaces/interface.py",
line 198, in __call__
return cls(self, x, name=name)
File
"/Users/Sage/sage-5.0.beta2/local/lib/python2.7/site-packages/sage/interfaces/interface.py",
line 625, in __init__
raise TypeError, x
TypeError: ECL says: Memory limit reached. Please jump to an outer pointer,
quit program and enlarge the memory limits before executing the program again.
Justin
--
Justin C. Walker, Curmudgeon-at-Large
() The ASCII Ribbon Campaign
/\ Help Cure HTML Email
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
Visit this group at http://groups.google.com/group/sage-support?hl=en.