On Wed, Feb 4, 2009 at 10:01 AM, Jaap Spies <j.sp...@hccnet.nl> wrote:
>
> mabshoff wrote:
>> Hello folks,
>>
>> 3.3.alpha5 is out and unlike 3.3.alpha4 it is being announced on sage-
>> devel. The main problem with alpha4 as you might have seen already was
>> that I broke the NTL dylib build while removing some code from sage-
>> env. Since then I also merged a bunch of other nice fixes (updated
>> m4ri, app bundle for OSX on bdist, TinyMCE polishing/fixes) and a also
>> fixed a couple doctests, so alpha5 is relatively small, but we need to
>> get it tested.
>>
>> Source tarball, a sage.math binary a the upgrade package can all be
>> found in the usual place at
>>
>>   http://sage.math.washington.edu/home/mabshoff/release-cycles-3.3/
>>
>> I already build and doctested this alpha5 on SkyNet, Solaris x86,
>> Sparc as well as OSX 64 bit and you should see only four doctest
>> failures:
>>
>> #5027: doctest failure for rings/polynomial/toy_d_basis.py [has an
>> agreed up fix, needs trivial patch]
>> #5166: Sage 3.3.a4: sage/symbolic/function.pyx doctest failure on OSX
>> [has a patch, needs review]
>> #5172: Sage 3.3.a5: more numerical noise in sage/calculus/calculus.py
>> [trivial to fix]
>> #5173: Sage 3.3.a5: doctest failure in sage/rings/polynomial/
>> polynomial_element.pyx due to print order of roots [cwitty? :)]
>>
>
> On Fedora 9, 32 bits I had those known issues
> plus 11 mysterious memory errors.

If we can't fix this fedora bug before the release, we *have* to put a
runtime check to see if Sage is
being run on fedora, and if so print a huge warning message on
startup.    What a mess.
I hope Michael's ideas to work around this problem in Singular work out.

William

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to