After pulling in today's coercion branch I get libSingular related
segfaults. Valgrind points at
/* "/scratch/mabshoff/release-cycle/sage-3.0.3-vg/devel/sage-main/
sage/rings/polynomial/multi_polynomial_libsingular.pyx":267
* raise NotImplementedError, "Only GF(q) and QQ are
suppor
Thanks for this release. This is as much as a birthday present.
All test passed!
Jaap
--~--~-~--~~~---~--~~
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 t
Hi,
I am almost ok with releasing rc0. I saw only one problem with any
doctests (I
did not finish doctesting yet on itanium linux).
There is *one* problem on our debian64 virtual machine on bsd. I guess you
saw this problem elsewhere:
[EMAIL PROTECTED]:~/build/sage-3.0.3.rc0$ ./sage -t
devel
Hello folks,
this is hopefully the final step toward 3.0.3. The release is much
later than I had hoped, but it should be a solid one. There are a
massive number of positively reviewed tickets in trac and many things
are going on that will be done at Dev1, but those will have to wait
for 3.0.4. Co
Hello folks,
here we go with alpha2. Things have been slower than thought, but this
ought to be it for the 3.0.3 release cycle since we need a build for
Dev1 in the next 24 hours.
There is a lot of stuff in trac and many things that are ready but did
not make it in. So not point in complaining a
Merged in alpha1:
#1440: Bjarke Hammersholt Roune:Inconsistency in subs and substitute
for univariate polynomials
#2353: Burcin Erocal: MPolynomialRing should be deprecated
#3111: John Cremona: Two bug fixes for elliptic curve abelian_group()
#3254: Mike Hansen: improvements and doctests
Hello folks,
this is Sage 3.0.3.alpha0. It looks like we we are continuing our
somewhat slow development pace while waiting for the coercion
rewrite to finish. Trac still has a staggering 75+ patches waiting
for review, so if you can spare a little time it would be nice if
you could review a patc
