I had an interesting failure on an intel mac running 10.5. Let me
describe my setup a bit since I think its relevant: because of the new
upgrade flexibility, I decided to have a "stable" sage and an
"unstable" sage on my machine, and I delete almost all of my other
sage builds. I changed the sage script in my /usr/bin to point to the
unstable one, which I called "wildsage". One of the sage folders I
deleted was for 3.2.1.rc0. With all that in mind, here is the error I
got in qqbar:
sage -t "devel/sage/sage/rings/qqbar.py"
Exception exceptions.TypeError: TypeError(RuntimeError('Unable to
start maxima',),) in 'sage.structure.parent_old._unregister_pair'
ignored
**********************************************************************
File "/Users/mh/sagestuff/wildsage/devel/sage/sage/rings/qqbar.py",
line 2556:
sage: QQbar(I) == QQbar(I * (2^100+1)/(2^100))
Exception raised:
Traceback (most recent call last):
File "/Users/mh/sagestuff/sage-3.2.1.rc0/local/bin/
ncadoctest.py", line 1231, in run_one_test
self.run_one_example(test, example, filename, compileflags)
File "/Users/mh/sagestuff/sage-3.2.1.rc0/local/bin/
sagedoctest.py", line 38, in run_one_example
OrigDocTestRunner.run_one_example(self, test, example,
filename, compileflags)
File "/Users/mh/sagestuff/sage-3.2.1.rc0/local/bin/
ncadoctest.py", line 1172, in run_one_example
compileflags, 1) in test.globs
File "<doctest __main__.example_64[3]>", line 1, in <module>
QQbar(I) == QQbar(I * (Integer(2)**Integer(100)+Integer(1))/
(Integer(2)**Integer(100)))###line 2556:
sage: QQbar(I) == QQbar(I * (2^100+1)/(2^100))
File "element.pyx", line 1102, in
sage.structure.element.RingElement.__mul__ (sage/structure/element.c:
8632)
File "coerce.pyx", line 663, in
sage.structure.coerce.CoercionModel_cache_maps.bin_op (sage/structure/
coerce.c:5359)
File "coerce.pyx", line 1079, in
sage.structure.coerce.CoercionModel_cache_maps.get_action (sage/
structure/coerce.c:9137)
File "coerce.pyx", line 1192, in
sage.structure.coerce.CoercionModel_cache_maps.discover_action (sage/
structure/coerce.c:10066)
File "parent.pyx", line 1063, in
sage.structure.parent.Parent.get_action (sage/structure/parent.c:9294)
File "parent_old.pyx", line 586, in
sage.structure.parent_old.Parent._get_action_ (sage/structure/
parent_old.c:6506)
File "parent_old.pyx", line 197, in
sage.structure.parent_old.Parent.get_action_c (sage/structure/
parent_old.c:2411)
File "parent_old.pyx", line 209, in
sage.structure.parent_old.Parent.get_action_impl (sage/structure/
parent_old.c:2698)
File "parent_old.pyx", line 268, in
sage.structure.parent_old.Parent.get_action_c_impl (sage/structure/
parent_old.c:3359)
File "parent_old.pyx", line 632, in
sage.structure.parent_old._register_pair (sage/structure/parent_old.c:
7314)
NotImplementedError: Infinite loop in multiplication of
0 (parent Symbolic Ring)
and 1 (parent Integer Ring)!
**********************************************************************
1 items had failures:
1 of 4 in __main__.example_64
***Test Failed*** 1 failures.
It looks like its trying to use the maxima from my deleted 3.2.1.rc0
build for some reason.
My ppc powerbook is still slaving away on tests, its almost done and
so far just has timeout failures on eisenstein and calculus.py.
-M. Hampton
On Dec 17, 12:20 pm, mabshoff <mabsh...@googlemail.com> wrote:
> Hello folks,
>
> here goes 3.2.2.rc1. We finally merge the Sage Words library and with
> that the last major piece of code is in 3.2.2. We also fixed a bad
> memory leak in coercion due to some debug code that snuck in. So 3.2.2
> should be very solid.
>
> Unfortunately there will be a 3.2.2.rc2 with at least an ATLAS update
> since the new sage.math needs excessive build time to build the
> current atlas.spkg. I attempted to monkey patch the fix in, but it
> doesn't work, so we will do the 3.8.2 upgrade in 3.2.2.rc2. But since
> Mike Hansen will rebase 12MB patches for the ReST transition very
> little new code and especially invasive patches will have to wait for
> 3.3.1 or 3.4 - depending if we need to do a quick bug fix release.
>
> Since the sage.math switchover to new hardware is imminent [it has
> been "tomorrow" for about two days now :)] I am sticking the tarball
> also on to sagemath.org. The sage.math only binary will not work on
> the new sage.math hardware, so I will not copy it over.
>
> Sources and a sage.math only binary is in
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.2/
>
> You can upgrade to this release by running
>
> ./sage
> -upgradehttp://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.2/sa...
>
> In case sage.math is down and/or unreachable the sources to upgrade as
> well as the tarball is temporarily at
>
> http://sagemath.org/temp/
>
> Please give this release a good beating and report any issues.
>
> Cheers,
>
> Michael
>
> #4237: William Stein: magma -- finite field matrix conversions
> [Reviewed by Michael Abshoff]
> #4639: Robert Bradshaw: bad memory leak with exponentiation [Reviewed
> by Michael Abshoff]
> #4653: Franco Saliola, Arnaud Bergeron, Amy Glen, Sebastien Labbe:
> Merge sage-words code into Sage [Reviewed by Mike Hansen]
> #4778: Ronan Paixao: Creates Scilab pexpect interface [Reviewed by
> Jaap Spies, Michael Abshoff]
> #4803: Sebastien Barthelemy: improvements to the polyhedra module
> documentation [Reviewed by Marshall Hampton]
> #4811: Gary Furnish: Sage 3.2.2.a2: doctesting line numbers in report
> are now wrong [Reviewed by Michael Abshoff]
> #4816: John Cremona: fix numerical noise issue in
> ell_rational_field.py [Reviewed by Michael Abshoff]
> #4819: Robert Bradshaw: update Cython to 0.10.3 [Reviewed by Michael
> Abshoff]
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
