Ok, some update:
"#2822: PolyBoRi segfault at exit" has been fixed and merged in Sage
3.0.alpha4. I am merging gcc 4.3 build support right now and plan to
release 3.0.alpha4 in the next 12 hours, i.e. in time before the
weekend push.
Cheers,
Michael
PS: Here is my ToDo list for 3.0:
List of blockers:
* #2195: Givaro-related crash in finite fields [x86 only, works fine
on x86-64]
* #2199: Copyright files for Debian packages [already partially
merged]
* #2303: bessel_I(1,1,"scipy") segfaults with gcc 4.2.3 on Linux x86
[nobody has been able to reproduce this so far. gcc 4.2.3
on x86-64 does not have this problem]
* #2344: python -- upgrade to version 2.5.2 [the spkg works fine,
but causes a segfault in integer.pyx on OSX. Getting this
spkg is essential for the 64 bit OSX port]
* #2347: better parsing for symbolics [with bundle, needs review]
* #2592: NTL abort in Integers(125)[]
* #2643: Fix Debian Sections [already partially merged]
* #2877: security risk -- several constructors use eval to parse
input
* #2851: clean binary install of sage followed by "sage -br" is
broken
Memory leaks:
* _fast_eval
* PolyBoRi
* latin squares
ToDo:
* revert ptest default
--~--~---------~--~----~------------~-------~--~----~
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://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
