[sage-devel] Trac Guidelines are now in the Wiki
Hello folks, there have been a large, nebulous set of rules regarding how things are done in trac, patch review and merging and the Sage development process in general. Now I finally took the time to clear those up and I put a *draft* of the guidelines up at http://wiki.sagemath.org/TracGuidelines What I wrote there is obviously not the final version and none of the rules are written in stone. I would actually like a discussion about the rules to clear any potential issue where things are either wrong or unclear. I consider what I wrote down the consensus from having done releases for the last four months, but even I do make mistakes ;) I am working on additional sections on workflow and so on. I believe that eventually the content of that Wiki page should go into the documentation or that at least a link from the official doc should point to that wiki page. Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] [Fwd: Re: benchmarking CAS]
From sci.math.symbolic See also the follow up. Original Message Subject: Re: benchmarking CAS Date: Sun, 30 Mar 2008 06:57:32 GMT From: Nasser Abbasi [EMAIL PROTECTED] Reply-To: Nasser Abbasi [EMAIL PROTECTED] Organization: SBC http://yahoo.sbc.com Newsgroups: sci.math.symbolic,sci.math References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Hello Vladimir; Vladimir Bondarenko [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] (The VM machine, if set to such a task, always crashes Maple, Mathematica, AXIOM, Maxima, Derive, and MuPAD; the concrete timing depends on the initial parameters. As of today, Derive 6.1 is the most stable computer algebra system of the above-listed. It would be interesting if your VM machine can add SAGE to the systems it tests. SAGE is described here: http://en.wikipedia.org/wiki/Software_for_Algebra_and_Geometry_Experimentation I played with SAGE a little, but I find its interface on windows, having to use a browser, a bit awkward to say the least. I have not tried it text based interface. Nasser --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 2.11.rc0 released!
On Sun, Mar 30, 2008 at 1:41 AM, mabshoff
[EMAIL PROTECTED] wrote:
here we go with 2.11.rc0. Hopefully this will be identical
to the final 2.11 release. So please build, doctest and
report all issues you hit.
On 32bit-intel Ubuntu 7.10 I had one failure, same as Jaap found but
with more detail:
[EMAIL PROTECTED]:~/sage$ sage -t devel/sage-main/sage/dsage/tests/testdoc.py
sage -t devel/sage-main/sage/dsage/tests/testdoc.pyException
exceptions.TypeError: TypeError('NoneType' object is not callable,)
in bound method Popen.__del__ of subprocess.Popen object at
0xa015ecc ignored
Exception in thread Thread-1 (most likely raised during interpreter shutdown):
Traceback (most recent call last):
File /home/carlo/sage/local/lib/python2.5/threading.py, line 460,
in __bootstrap
File
/home/carlo/sage/local/lib/python2.5/site-packages/sage/dsage/interface/dsage_interface.py,
line 46, in run
File
/home/carlo/sage/local/lib/python2.5/site-packages/twisted/internet/posixbase.py,
line 220, in run
File
/home/carlo/sage/local/lib/python2.5/site-packages/twisted/internet/posixbase.py,
line 233, in mainLoop
type 'exceptions.AttributeError': 'NoneType' object has no attribute 'msg'
Unhandled exception in thread started by
Error in sys.excepthook:
Original exception was:
[18.6 s]
exit code: 1024
--
The following tests failed:
sage -t devel/sage-main/sage/dsage/tests/testdoc.py
Total time for all tests: 18.6 seconds
--
Carlo Hamalainen
http://carlo-hamalainen.net
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 2.11.rc0 released!
On Mar 30, 2:13 pm, Carlo Hamalainen [EMAIL PROTECTED] wrote: On Sun, Mar 30, 2008 at 1:41 AM, mabshoff [EMAIL PROTECTED] wrote: here we go with 2.11.rc0. Hopefully this will be identical to the final 2.11 release. So please build, doctest and report all issues you hit. On 32bit-intel Ubuntu 7.10 I had one failure, same as Jaap found but with more detail: [EMAIL PROTECTED]:~/sage$ sage -t devel/sage-main/sage/dsage/tests/testdoc.py SNIP Carlo, Jaap thanks for the repo. I don't consider this a show stopper. Yi: Do you have any idea what is wrong here? Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Trac Guidelines are now in the Wiki
On Mar 30, 2008, at 6:31 AM, mabshoff wrote: Hello folks, there have been a large, nebulous set of rules regarding how things are done in trac, patch review and merging and the Sage development process in general. Now I finally took the time to clear those up and I put a *draft* of the guidelines up at http://wiki.sagemath.org/TracGuidelines What I wrote there is obviously not the final version and none of the rules are written in stone. I would actually like a discussion about the rules to clear any potential issue where things are either wrong or unclear. I consider what I wrote down the consensus from having done releases for the last four months, but even I do make mistakes ;) I am working on additional sections on workflow and so on. I believe that eventually the content of that Wiki page should go into the documentation or that at least a link from the official doc should point to that wiki page. On a quick skim-read, I found the Sage Specific paragraph very confusing. Are you trying to say that if someone makes up their own version of Sage that ships different versions of packages to the ones we normally ship, then they are on their own? Or something else? david --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Trac Guidelines are now in the Wiki
On Mar 30, 3:50 pm, David Harvey [EMAIL PROTECTED] wrote: On Mar 30, 2008, at 6:31 AM, mabshoff wrote: Hello folks, there have been a large, nebulous set of rules regarding how things are done in trac, patch review and merging and the Sage development process in general. Now I finally took the time to clear those up and I put a *draft* of the guidelines up at http://wiki.sagemath.org/TracGuidelines What I wrote there is obviously not the final version and none of the rules are written in stone. I would actually like a discussion about the rules to clear any potential issue where things are either wrong or unclear. I consider what I wrote down the consensus from having done releases for the last four months, but even I do make mistakes ;) I am working on additional sections on workflow and so on. I believe that eventually the content of that Wiki page should go into the documentation or that at least a link from the official doc should point to that wiki page. On a quick skim-read, I found the Sage Specific paragraph very confusing. Are you trying to say that if someone makes up their own version of Sage that ships different versions of packages to the ones we normally ship, then they are on their own? Or something else? Short answer: yes. If that person experiences bugs with that version of Sage they are on their own. They can ask for support and I will do my best to help them, but that problem doesn't belong in out trac. Long answer: This is directed toward distribution specific packaging of Sage when certain components like gmp, pari, GAP that are already in the distribution are replaced by those distribution specific versions. In that case I don't think we should trac those issues since those distributions have their own trackers and I am perfectly content with fixing bugs in the official version of Sage. Any ticket in the Sage tracker should be about the official Sage release, i.e. we should be able to resolve the issue. If your maxima breaks because you are using gcl 2.6.8 on FUBAR Linux: Not my problem. Our resources shouldn't be spend on those issues, we have plenty of our own bugs to fix. Once you replace components of Sage you get a combinatorial explosion of configurations and there is no way that we can support it. William started packaging all those components exactly because of the combinatorial explosion problem as well as the difficulty of even compiling all of Sage's components way back when Sage was much smaller. So: where to draw the line? I think we should interpret this very tightly and only support the official release because otherwise there is no reasonable rule to apply. For example: I swapped clisp for cumcl on Solaris and it broke a bunch of Maxima tests. I upgrade Maxima from 5.13.0 to 5.14.0 and it broke about five doctests. You see that even small and innocent looking changes lead to a bunch of problems. I am not saying that people can't or shouldn't do that, I am just saying I prefer not to carry a myriad of impossible to resolve bug reports in out trac. Let the distributions deal with that problem. If Sage were to release every six to twelve months the issue would probably be slightly different, but as long as Sage is moving as fast as it currently is I don't think that using anything but a build from source or the official binaries will ever get you close to the optimal Sage experience. For the record: That rule came specifically from the following tickets: #2728: doctest failures for maxima in Debian packaged sage 2.10.4 This is not Sage Specific: It might be due to Debian packaging an older version of Maxima or alternatively be caused by using gcl instead of clisp. It is certainly borderline, but I don't think in this case it is on our end to fix this. #2730: matplotlib in Debian is too old This is not Sage Specific: Please file a bug report with Debian or alternatively package the Sage version of matplotlib. #2731: GeneratorMatCode doesn't seem to be available in Debian's GAP This is not Sage Specific: Please file a bug report with Debian or alternatively package the Sage version of GAP. Alternatively create a deb which contains the GAP packages that Sage installs per default. #2733: PARI in Debian has the mathnf bug This is not Sage Specific: This is a packaging bug in Debian's pari.deb and should be filed as a bug report at the Debian bug tracker. #2734: SAGE Debian doctest errors whose cause I don't understand Sorry Tim, this should go to debian-sage or sage-devel. One Issue Per Ticket hasn't been met. I consider none of those our problem and while I am certain that Tim would be willing and able to resolve most of the above tickets they do not belong in our trac. When I evaluate software one of the first things I check is their bug database and if a) they don't have on b) it is full of old, unresolved bugs it immediately raises a red flag for me. I don't want this to happen to Sage, hence no
[sage-devel] Re: Trac Guidelines are now in the Wiki
On a quick skim-read, I found the Sage Specific paragraph very confusing. Are you trying to say that if someone makes up their own version of Sage that ships different versions of packages to the ones we normally ship, then they are on their own? Or something else? david One more thing I forgot: This is like the Linux kernel, i.e. if you load a binary module your kernel gets tainted. People will do their best to help you [modulo some preaching not to use evil binary modules], but in the end that is *your* problem. Using different Sage components doesn't have the same stigma attached to say the NVidia binary driver, but if you choose to do things differently and shoot yourself in the foot it is *your* problem because you didn't want to listen ;) Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 2.11.rc0 released!
I get the same as Carlo.
John
On Mar 30, 1:13 pm, Carlo Hamalainen [EMAIL PROTECTED]
wrote:
On Sun, Mar 30, 2008 at 1:41 AM, mabshoff
[EMAIL PROTECTED] wrote:
here we go with 2.11.rc0. Hopefully this will be identical
to the final 2.11 release. So please build, doctest and
report all issues you hit.
On 32bit-intel Ubuntu 7.10 I had one failure, same as Jaap found but
with more detail:
[EMAIL PROTECTED]:~/sage$ sage -t devel/sage-main/sage/dsage/tests/testdoc.py
sage -t devel/sage-main/sage/dsage/tests/testdoc.pyException
exceptions.TypeError: TypeError('NoneType' object is not callable,)
in bound method Popen.__del__ of subprocess.Popen object at
0xa015ecc ignored
Exception in thread Thread-1 (most likely raised during interpreter shutdown):
Traceback (most recent call last):
File /home/carlo/sage/local/lib/python2.5/threading.py, line 460,
in __bootstrap
File
/home/carlo/sage/local/lib/python2.5/site-packages/sage/dsage/interface/dsage_interface.py,
line 46, in run
File
/home/carlo/sage/local/lib/python2.5/site-packages/twisted/internet/posixbase.py,
line 220, in run
File
/home/carlo/sage/local/lib/python2.5/site-packages/twisted/internet/posixbase.py,
line 233, in mainLoop
type 'exceptions.AttributeError': 'NoneType' object has no attribute 'msg'
Unhandled exception in thread started by
Error in sys.excepthook:
Original exception was:
[18.6 s]
exit code: 1024
--
The following tests failed:
sage -t devel/sage-main/sage/dsage/tests/testdoc.py
Total time for all tests: 18.6 seconds
--
Carlo Hamalainenhttp://carlo-hamalainen.net
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 2.11.rc0 released!
I get this also, on a G4 mac running 10.4.11.
My make test got hung up in a strange way and my terminal seemed
corrupted, but I think that was because firefox crashed doing some
jmol stuff and its probably irrelevent. I reran the test where it
hung and it passed (sage/interfaces/expect.py)
-M. Hampton
On Mar 30, 10:08 am, John Cremona [EMAIL PROTECTED] wrote:
I get the same as Carlo.
John
On Mar 30, 1:13 pm, Carlo Hamalainen [EMAIL PROTECTED]
wrote:
On Sun, Mar 30, 2008 at 1:41 AM, mabshoff
[EMAIL PROTECTED] wrote:
here we go with 2.11.rc0. Hopefully this will be identical
to the final 2.11 release. So please build, doctest and
report all issues you hit.
On 32bit-intel Ubuntu 7.10 I had one failure, same as Jaap found but
with more detail:
[EMAIL PROTECTED]:~/sage$ sage -t
devel/sage-main/sage/dsage/tests/testdoc.py
sage -t devel/sage-main/sage/dsage/tests/testdoc.pyException
exceptions.TypeError: TypeError('NoneType' object is not callable,)
in bound method Popen.__del__ of subprocess.Popen object at
0xa015ecc ignored
Exception in thread Thread-1 (most likely raised during interpreter
shutdown):
Traceback (most recent call last):
File /home/carlo/sage/local/lib/python2.5/threading.py, line 460,
in __bootstrap
File
/home/carlo/sage/local/lib/python2.5/site-packages/sage/dsage/interface/dsage_interface.py,
line 46, in run
File
/home/carlo/sage/local/lib/python2.5/site-packages/twisted/internet/posixbase.py,
line 220, in run
File
/home/carlo/sage/local/lib/python2.5/site-packages/twisted/internet/posixbase.py,
line 233, in mainLoop
type 'exceptions.AttributeError': 'NoneType' object has no attribute 'msg'
Unhandled exception in thread started by
Error in sys.excepthook:
Original exception was:
[18.6 s]
exit code: 1024
--
The following tests failed:
sage -t devel/sage-main/sage/dsage/tests/testdoc.py
Total time for all tests: 18.6 seconds
--
Carlo Hamalainenhttp://carlo-hamalainen.net
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 2.11.rc0 released!
Hi,
rc0 -- On every single test machine
sage -t devel/sage-main/sage/dsage/tests/testdoc.py
fails.
On Meccah (athlon 32-bit):
sage -t devel/sage-main/sage/interfaces/psage.py
sage -t devel/sage-main/sage/interfaces/sage0.py
sage -t devel/sage-main/sage/misc/functional.py
sage -t devel/sage-main/sage/dsage/tests/testdoc.py
sage -t devel/sage-main/sage/rings/quotient_ring.py
sage -t devel/sage-main/sage/calculus/calculus.py
Total time for all tests: 17848.8 seconds
See /home/was/build/tests/meccah.log for the log.
William
On Sun, Mar 30, 2008 at 8:08 AM, John Cremona [EMAIL PROTECTED] wrote:
I get the same as Carlo.
John
On Mar 30, 1:13 pm, Carlo Hamalainen [EMAIL PROTECTED]
wrote:
On Sun, Mar 30, 2008 at 1:41 AM, mabshoff
[EMAIL PROTECTED] wrote:
here we go with 2.11.rc0. Hopefully this will be identical
to the final 2.11 release. So please build, doctest and
report all issues you hit.
On 32bit-intel Ubuntu 7.10 I had one failure, same as Jaap found but
with more detail:
[EMAIL PROTECTED]:~/sage$ sage -t
devel/sage-main/sage/dsage/tests/testdoc.py
sage -t devel/sage-main/sage/dsage/tests/testdoc.pyException
exceptions.TypeError: TypeError('NoneType' object is not callable,)
in bound method Popen.__del__ of subprocess.Popen object at
0xa015ecc ignored
Exception in thread Thread-1 (most likely raised during interpreter
shutdown):
Traceback (most recent call last):
File /home/carlo/sage/local/lib/python2.5/threading.py, line 460,
in __bootstrap
File
/home/carlo/sage/local/lib/python2.5/site-packages/sage/dsage/interface/dsage_interface.py,
line 46, in run
File
/home/carlo/sage/local/lib/python2.5/site-packages/twisted/internet/posixbase.py,
line 220, in run
File
/home/carlo/sage/local/lib/python2.5/site-packages/twisted/internet/posixbase.py,
line 233, in mainLoop
type 'exceptions.AttributeError': 'NoneType' object has no attribute
'msg'
Unhandled exception in thread started by
Error in sys.excepthook:
Original exception was:
[18.6 s]
exit code: 1024
--
The following tests failed:
sage -t devel/sage-main/sage/dsage/tests/testdoc.py
Total time for all tests: 18.6 seconds
--
Carlo Hamalainenhttp://carlo-hamalainen.net
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 2.11.rc0 released!
On an (old) ubuntu 7.10 amd64 machine, s.11.rc0 installed fine but
sage -testall has hung 3 times (as of now). I ctl-C'd and restarted.
It has hung on const.tex, calculus.py, and special.py.
Failures so far in testdoc.py and weierstrass_morphism.py:
sage -t devel/sage-main/sage/dsage/tests/testdoc.pyException
exceptions.TypeError: TypeError('NoneType' object is not callable,)
in bound method Popen.__del__ of subprocess.Popen object at
0x35e6a10 ignored
Exception in thread Thread-1 (most likely raised during interpreter shutdown):
Traceback (most recent call last):
File /home/wdj/wdj/sagefiles/sage-2.11.rc0/local/lib/python2.5/threading.py,
line 460, in __bootstrap
File
/home/wdj/wdj/sagefiles/sage-2.11.rc0/local/lib/python2.5/site-packages/sage/dsage/interface/dsage_interface.py,
line 46, in run
File
/home/wdj/wdj/sagefiles/sage-2.11.rc0/local/lib/python2.5/site-packages/twisted/internet/posixbase.py,
line 220, in run
File
/home/wdj/wdj/sagefiles/sage-2.11.rc0/local/lib/python2.5/site-packages/twisted/internet/posixbase.py,
line 233, in mainLoop
type 'exceptions.AttributeError': 'NoneType' object has no attribute 'msg'
Unhandled exception in thread started by
Error in sys.excepthook:
Original exception was:
sage -t
devel/sage-main/sage/schemes/elliptic_curves/weierstrass_morphism.py**
File weierstrass_morphism.py, line 125:
sage: var('u r s t'); w=baseWI(u,r,s,t)
Exception raised:
Traceback (most recent call last):
File
/home/wdj/wdj/sagefiles/sage-2.11.rc0/local/lib/python2.5/doctest.py,
line 1212, in __run
compileflags, 1) in test.globs
File doctest __main__.example_6[5], line 1, in module
var('u r s t'); w=baseWI(u,r,s,t)###line 125:
sage: var('u r s t'); w=baseWI(u,r,s,t)
File
/home/wdj/wdj/sagefiles/sage-2.11.rc0/local/lib/python2.5/site-packages/sage/schemes/elliptic_curves/weierstrass_morphism.py,
line 52, in __init__
if u==0:
File
/home/wdj/wdj/sagefiles/sage-2.11.rc0/local/lib/python2.5/site-packages/sage/calculus/equations.py,
line 786, in __nonzero__
s = m.parent()._eval_line('is (%s)'%m.name())
File
/home/wdj/wdj/sagefiles/sage-2.11.rc0/local/lib/python2.5/site-packages/sage/interfaces/maxima.py,
line 549, in _eval_line
self._synchronize()
File
/home/wdj/wdj/sagefiles/sage-2.11.rc0/local/lib/python2.5/site-packages/sage/interfaces/maxima.py,
line 618, in _synchronize
self._interrupt()
File
/home/wdj/wdj/sagefiles/sage-2.11.rc0/local/lib/python2.5/site-packages/sage/interfaces/maxima.py,
line 494, in _interrupt
self._expect_expr(timeout=2)
File
/home/wdj/wdj/sagefiles/sage-2.11.rc0/local/lib/python2.5/site-packages/sage/interfaces/maxima.py,
line 462, in _expect_expr
raise ValueError, %s\nComputation failed due to a bug in
Maxima -- NOTE: Maxima had to be restarted.%v
ValueError: sconc(__SAGE_SYNCHRO_MARKER_,(1249016650+1)
** - Continuable Error
PRINT: User break
If you continue (by typing 'continue'): Continue execution
The following restarts are also available:
MACSYMA-QUIT :R1 Maxima top-level
Computation failed due to a bug in Maxima -- NOTE: Maxima had to
be restarted.
**
File weierstrass_morphism.py, line 127:
sage: ~w
Expected:
(1/u, -r/u^2, -s/u, (r*s - t)/u^3)
Got:
(1/2, -3/4, -2, 7/8)
**
1 items had failures:
2 of 8 in __main__.example_6
***Test Failed*** 2 failures.
On Sat, Mar 29, 2008 at 7:41 PM, mabshoff
[EMAIL PROTECTED] wrote:
Hello folks,
here we go with 2.11.rc0. Hopefully this will be identical
to the final 2.11 release. So please build, doctest and
report all issues you hit. We thing we have fixed all
reported doctest failures. Depending on whether issues do
crop up we might do a 2.11.final or if things go really
bad an 2.11.rc1.
The source tarball [195MB] is at
http://sage.math.washington.edu/home/mabshoff/release-cycles-2.11/sage-2.11.rc0.tar
The sage.math only build [282MB] is at
http://sage.math.washington.edu/home/mabshoff/release-cycles-2.11/sage-2.11.rc0-sage.math-only-x86_64-Linux.tar.gz
Time to catch some sleep for me.
Cheers,
Michael
Merged in rc0:
#1882: Marshall Hampton, Carl Witty: update optional
phcpack.spkg to 2.3.39, mixed volume computation
#1990: Carl Witty: ZZ.random_element() -- never returns
0 and typos/nonsense in docstrings
#2173: Tim Abbott: SAGE setup.py should run cython as
python2.5 cython and other debian fixes
#2688: Emily Kirkman: Kuratowski subgraph isolator for
planarity checking
#2702: Martin Albrecht, Mike Hansen: get coverage of
multi_polynomial_libsingular to almost 100%
#2709: Nick Alexander: add a prime_above() function to
[sage-devel] Re: Sage 2.11.rc0 released!
On Sun, Mar 30, 2008 at 5:44 AM, mabshoff [EMAIL PROTECTED] wrote: On Mar 30, 2:13 pm, Carlo Hamalainen [EMAIL PROTECTED] wrote: On Sun, Mar 30, 2008 at 1:41 AM, mabshoff [EMAIL PROTECTED] wrote: here we go with 2.11.rc0. Hopefully this will be identical to the final 2.11 release. So please build, doctest and report all issues you hit. On 32bit-intel Ubuntu 7.10 I had one failure, same as Jaap found but with more detail: [EMAIL PROTECTED]:~/sage$ sage -t devel/sage-main/sage/dsage/tests/testdoc.py SNIP Carlo, Jaap thanks for the repo. I don't consider this a show stopper. Yi: Do you have any idea what is wrong here? I am working on it right now but I don't have a clear answer yet. Googling for thread safety of subprocess.Popen did come up with some interesting results though. I agree that this isn't a show stopper since the tests do actually pass. If you look carefully, the exception gets thrown on shutdown. Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] install fail on Suse ia64
I use Suse enterprise server 9 sp2-ia64, below is the 'uname -a' result. Linux linux 2.6.5-7.191-sn2 #1 SMP Tue Jun 28 14:58:56 UTC 2005 ia64 ia64 ia64 GNU/Linux compiler is gcc (GCC) 3.3.3 (SuSE Linux) The first error was encountered in periods.cc where an ambiguous call. It is a pity that I cannot debug myself because unresolved namespace NTL problem happened after I followed the self-debug instruction. Any idea to over it? Regards, -- periods.cc: In constructor `periods_via_lfchi::periods_via_lfchi(const level*, const newform*)': periods.cc:382: error: call of overloaded `log(int)' is ambiguous /usr/include/bits/mathcalls.h:110: error: candidates are: double log(double) /usr/include/g++/cmath:419: error: long double std::log(long double) /usr/include/g++/cmath:411: error: float std::log(float) periods.cc:383: error: call of overloaded `log(int)' is ambiguous /usr/include/bits/mathcalls.h:110: error: candidates are: double log(double) /usr/include/g++/cmath:419: error: long double std::log(long double) /usr/include/g++/cmath:411: error: float std::log(float) periods.cc: In member function `virtual void periods_direct::compute()': periods.cc:459: error: call of overloaded `log(int)' is ambiguous /usr/include/bits/mathcalls.h:110: error: candidates are: double log(double) /usr/include/g++/cmath:419: error: long double std::log(long double) /usr/include/g++/cmath:411: error: float std::log(float) periods.cc:460: error: call of overloaded `log(int)' is ambiguous /usr/include/bits/mathcalls.h:110: error: candidates are: double log(double) /usr/include/g++/cmath:419: error: long double std::log(long double) /usr/include/g++/cmath:411: error: float std::log(float) periods.cc: In member function `virtual void part_period::compute()': periods.cc:554: error: call of overloaded `log(int)' is ambiguous /usr/include/bits/mathcalls.h:110: error: candidates are: double log(double) /usr/include/g++/cmath:419: error: long double std::log(long double) /usr/include/g++/cmath:411: error: float std::log(float) periods.cc: In member function `void ldash1::init(const level*, const std::vectorlong int, std::allocatorlong int , long int, const rational)': periods.cc:593: error: call of overloaded `log(int)' is ambiguous /usr/include/bits/mathcalls.h:110: error: candidates are: double log(double) /usr/include/g++/cmath:419: error: long double std::log(long double) /usr/include/g++/cmath:411: error: float std::log(float) periods.cc: In constructor `lfchi::lfchi(const level*, const newform*)': periods.cc:635: error: call of overloaded `log(int)' is ambiguous /usr/include/bits/mathcalls.h:110: error: candidates are: double log(double) /usr/include/g++/cmath:419: error: long double std::log(long double) /usr/include/g++/cmath:411: error: float std::log(float) periods.cc: In function `NTL::RR G(int, NTL::RR)': periods.cc:975: error: call of overloaded `log(int)' is ambiguous /usr/include/bits/mathcalls.h:110: error: candidates are: double log(double) /usr/include/g++/cmath:419: error: long double std::log(long double) /usr/include/g++/cmath:411: error: float std::log(float) make[3]: *** [periods_n.o] Error 1 make[3]: Leaving directory `/root/sage-2.10.4/spkg/build/eclib-20080127.p1/src/g0n' make[2]: *** [all] Error 2 make[2]: Leaving directory `/root/sage-2.10.4/spkg/build/eclib-20080127.p1/src' Error building cremona real9m3.113s user8m53.577s sys 0m9.314s sage: An error occurred while installing eclib-20080127.p1 Please email sage-devel http://groups.google.com/group/sage-devel explaining the problem and send the relevant part of of /root/sage-2.10.4/install.log. Describe your computer, operating system, etc. If you want to try to fix the problem, yourself *don't* just cd to /root/sage-2.10.4/spkg/build/eclib-20080127.p1 and type 'make'. Instead type /root/sage-2.10.4/sage -sh in order to set all environment variables correctly, then cd to /root/sage-2.10.4/spkg/build/eclib-20080127.p1 (When you are done debugging, you can type exit to leave the subshell.) make[1]: *** [installed/eclib-20080127.p1] Error 1 make[1]: Leaving directory `/root/sage-2.10.4/spkg' -- guez offtsing [EMAIL PROTECTED] IAP --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: install fail on Suse ia64
On Mar 31, 3:10 am, guez offtsing [EMAIL PROTECTED] wrote: I use Suse enterprise server 9 sp2-ia64, below is the 'uname -a' result. Linux linux 2.6.5-7.191-sn2 #1 SMP Tue Jun 28 14:58:56 UTC 2005 ia64 ia64 ia64 GNU/Linux compiler is gcc (GCC) 3.3.3 (SuSE Linux) The first error was encountered in periods.cc where an ambiguous call. It is a pity that I cannot debug myself because unresolved namespace NTL problem happened after I followed the self-debug instruction. Any idea to over it? Regards, Hi, we require at least gcc 3.4 or higher since we need a compiler that is implements the c99 standard. Sage should tell you right away that the compiler you are using doesn't meet the minimum requirement. We will hopefully fix that in the next release. Right now it tells you that when you would build FLINT, which happens to be after the problem you see right now. Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: install fail on Suse ia64
On Mar 31, 3:10 am, guez offtsing [EMAIL PROTECTED] wrote: SNIP /usr/include/g++/cmath:411: error: float std::log(float) periods.cc: In function `NTL::RR G(int, NTL::RR)': periods.cc:975: error: call of overloaded `log(int)' is ambiguous /usr/include/bits/mathcalls.h:110: error: candidates are: double log(double) /usr/include/g++/cmath:419: error: long double std::log(long double) /usr/include/g++/cmath:411: error: float std::log(float) make[3]: *** [periods_n.o] Error 1 make[3]: Leaving directory `/root/sage-2.10.4/spkg/build/eclib-20080127.p1/src/g0n' make[2]: *** [all] Error 2 make[2]: Leaving directory `/root/sage-2.10.4/spkg/build/eclib-20080127.p1/src' Error building cremona Either way: This issue in eclib is likely to be fixable. John: should I roll you a patch? I am not sure if people desire a stand alone mwranl and supporting older gcc releases might come in handy there. Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Frobby: Software for computations on monomial ideals
On 30 Mar., 19:15, David Joyner [EMAIL PROTECTED] wrote: Just a few ideas. Hopefully someone who is more of an expert on commutative algebra computations will weigh in. The usual procedure is to (1) make an optional SAGE package (spkg file - see the programming manual, maybe use the macaulay interface as a model) (2) announce it to sage-devel and file a ticket for it on trac, asking for comments. This seems like a good way to go about it. Thank you for the advice. SAGE already has gfan. I haven't used it but my understanding is that it is also a package for commutive algebra computations for monomial ideals. Maybe you could compare them? Are there Grobner bases computations which both frobby and gfan can do? Does it do any toric variety computations? Frobby performs computations on monomial ideals that you have already obtained somehow - it does not do things like compute initial ideals. Thus Frobby and Gfan complement each other, since Gfan does not do computations on monomial ideals (except that it can draw them in three dimensions). Gfan does output monomial ideals, which Frobby can then process further. It's funny - I had not explicitly thought about the fact that these programs compliment each other well, despite my good friend Anders N. Jensen (who is the author of Gfan) having been my office mate for a year. It must be because most non-random ideals that I've been dealing with have been produced by the program 4ti2. Cheers Bjarke --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Frobby: Software for computations on monomial ideals
On Sun, Mar 30, 2008 at 6:38 PM, Bjake Hammersholt Roune [EMAIL PROTECTED] wrote: On 30 Mar., 19:15, David Joyner [EMAIL PROTECTED] wrote: Just a few ideas. Hopefully someone who is more of an expert on commutative algebra computations will weigh in. The usual procedure is to (1) make an optional SAGE package (spkg file - see the programming manual, maybe use the macaulay interface as a model) (2) announce it to sage-devel and file a ticket for it on trac, asking for comments. This seems like a good way to go about it. Thank you for the advice. SAGE already has gfan. I haven't used it but my understanding is that it is also a package for commutive algebra computations for monomial ideals. Maybe you could compare them? Are there Grobner bases computations which both frobby and gfan can do? Does it do any toric variety computations? Frobby performs computations on monomial ideals that you have already obtained somehow - it does not do things like compute initial ideals. Thus Frobby and Gfan complement each other, since Gfan does not do computations on monomial ideals (except that it can draw them in three dimensions). Gfan does output monomial ideals, which Frobby can then process further. It's funny - I had not explicitly thought about the fact that these programs compliment each other well, despite my good friend Anders N. Jensen (who is the author of Gfan) having been my office mate for a year. It must be because most non-random ideals that I've been dealing with have been produced by the program 4ti2. I just want to point out quickly that we (=Sage devel community) also have an interest in including 4ti2 in Sage at some point, if somebody were to come along and do the integration work (hint, hint). William --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] sage-2.11 is out!
Hello folks, Sage 2.11 has been released on March 30th, 2008. It is available at http://sagemath.org/download.html I will post binaries sometime this evening. * About Sage (http://www.sagemath.org) Sage is developed by volunteers and combines 71 open source packages. It is available for download from sagemath.org and its mirrors in source or binary form. If you have any questions and/or problems please report them to the google groups sage-devel or sage-support. You can also drop by in #sage-devel or #sage-support in freenode. - The following 31 people contributed code to this release: * Tim Abbott * Michael Abshoff * Martin Albrecht * Nick Alexander * Tom Boothby * Robert Bradshaw * Craig Citro * John Cremona * Dan Drake * Didier Deshommes * Burcin Erocal * Lars Fischer * Gary Furnish * Alex Ghitza * Jason Grout * Marshall Hampton * Carlo Hamalainen * Mike Hansen * Ryan Hinton * David Joyner * Michael Kallweit * Emily Kirkman * Robert Miller * Joel Mohler * R. Rishikesh * David Roe * William Stein * Jaap Spies * Justin Walker * Carl Witty * Yi Qiang Cheers, Michael Abshoff (release chair), William Stein * Major Features, New Spkgs and Bugfixes * ATLAS: Michael Abshoff and Burcin Erocal upgraded ATLAS to the 3.8.1 release. In addition tuning info for 32 bit Prescott CPUs as well as Powerbook G4s under Linux was added. * zn_poly: David Harvey's zn_poly library is now a standard package for Sage. zn_poly is a new C library for polynomial arithmetic in (Z/nZ)[x] where 3≤n≤ULONG_MAX (i.e. any machine-word-sized modulus). The main benefit is speed. The library is used so far only to compute the zeta function for hyperelliptic curves. * Small roots method for polynomials mod N (N composite): Martin Albrecht implemented Coppersmith's method for finding small roots of univariate polynomials modulo N where N is composite. * Generic Multivariate Polynomial Arithmetic: Joel Mohler improved the efficiency of the generic multivariate polynomial arithmetic in Sage by roughly a factor of ten. * k-Schur Functions and Non-symmetric Macdonald Polynomials: Mike Hansen: k-Schur functions s^(k)_\lambda are a relatively new family of symmetric functions which play a role in Z[h1,...,hk] as the Schur functions s_\lambda do in \Lambda. The k-Schur functions, amongst other things, provide a natural basis for the quantum cohomology of the Grassmannian. The k-Schur functions can be used like any other symmetric functions and are created with kSchurFunctions. Non-symmetric Macdonald polynomials in type A can now be accessed in Sage. The polynomials are computed from the main theorem in A Combinatorial Formula for the Non-symmetric Macdonald Polynomials by Haglun, Haiman, and Loehr. * Marshall Hampton did upgrade gfan as well as the optional phcpack spkgs and their interfaces. He also increased doctest coverage to 100% for both interfaces. * Improved capabilities for solving matrix equations: William Stein implemented code so that one can now solve matrix equations AX=B and XA=B whenever a solution exists. In particular, solving linear equations now works even if A is singular or nonsquare. * Generators for congruence subgroups: Robert Miller implemented an algorithm for very quickly computing generators for congruence subgroups \Gamma_0(N), \Gamma_1(N), and \Gamma_H(N). * Various other people fixed a number of bugs and did improve other bits of Sage. * Known Issues with 2.11: * None * Bug Statistics We closed 129 tickets. For details see http://trac.sagemath.org/sage_trac/milestone/sage-2.11 or check out the closed ticket section at the end of the announcement. * Upcoming Releases The next release will be 3.0, chaired by Michael Abshoff. The release is planned in about two weeks. Potential features include: * DOCTESTS: Raise the doctest coverage of the Sage library to 50%. * INTERACT: Interactive versions of functions in the notebook; kind of like Mathematica's Manipulate command. * R: a pexpect R interface * TIMING/BENCHMARK: Making it so doctesting Sage also saves complete timing and profiling information. Start using and publishing the results of this. * PORTING: OSX 10.5 64 bit, FreeBSD, PPC 64 bit build support out of the box. Experimental 32 bit Solaris 10 build support. * MODULAR ABELIAN VARIETIES: Implement Stein's algorithms for computing with modular abelian varieties. This is very symbolic, because Stein started the Sage project in the first place specifically to implement these algorithms. * Doctesting Coverage For 2.10.4 we had: Overall weighted coverage score: 47.6% Total number of functions: 18616 We increased coverage by 1.3% in 2.11 while adding 237 functions: Overall weighted coverage score: 48.9% Total number of functions: 18853 * Closed
