[sage-devel] Re: sage-1.5.0.2

2006-12-17 Thread Joshua Kantor
I tried to do sage upgrade, everything appeared to succeed but when I try to start sage I get. Traceback (most recent call last) /home/jkantor/sage-1.4/local/bin/ in () /home/jkantor/sage-1.4/local/lib/python2.5/site-packages/sage/all_cmdline.py in () > 1 from sage.all import *

[sage-devel] Re: sage-1.5.0.2

2006-12-17 Thread William Stein
You need to delete all the interrupt.h files under the devel/sage/sage tree. This should be done automatically by the upgraded script, at least in sage-1.5.1.2. But you can easily do it manually, then type "sage -ba": rm -f */interrupt.h */*/interrupt.h */*/*/interrupt.h */*/*/*/interrupt.

[sage-devel] Re: sage-1.5.0.2

2006-12-17 Thread Joshua Kantor
That worked, thanks. Josh --~--~-~--~~~---~--~~ 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:/

[sage-devel] Re: Graph Question

2006-12-17 Thread Robert Miller
Martin, The short answer is that the graph code in sage right now doesn't have any options to tweak the automatic spring layout. In other words, my wrapping isn't done. You can, however, reach through to NetworkX as in the following example. Suppose I have some graph G: G = graphs.RandomGNP(27,.

[sage-devel] Proper way to add/delete files to the codebase?

2006-12-17 Thread Nick Alexander
What is the proper way to add a file to the codebase? I create, hg_sage.add(), hg_sage.commit(), sage -b, etc but the changes are not reflected in the build directory. Same with deletion -- what is the proper way to delete a file? Thanks, Nick --~--~-~--~~~---~--~-

[sage-devel] Testing code in misc

2006-12-17 Thread Nick Alexander
Hi everyone, I'm having trouble testing functions in misc/*, running a fairly heavily modded sage-alpha8. Everything in rings/* works fine. If I copy the file misc/.doctest/sageinspect.py to rings/.doctest/sageinspect.py, everything works fine. The error log is: ~/Devel/sage/devel/sage-was/sa

[sage-devel] Documentation format

2006-12-17 Thread Georg Muntingh
I noticed that the documentation format doesn't contain a 'see also-section'. When using a CAS I always think such sections to be very useful, because it often provides a convenient method for finding the function I'm looking for. Maybe there is a good reason that they are not there, but at the m

[sage-devel] notebook usage

2006-12-17 Thread William Stein
Martin wrote (on trac #185): "On my P4 so as my P3 system whenever I undertake a long calculation using the notebook the polling for results takes way too much cputime. I guess it's caused by a very high polling frequency. top output follows: martin25 0 125m 36m 9.8m R 80 2.4

[sage-devel] Re: SAGE \rightarrow SAGE

2006-12-17 Thread William Stein
On Fri, 15 Dec 2006 16:23:57 -0800, Iftikhar Burhanuddin <[EMAIL PROTECTED]> wrote: > > While we are on the subject of logos, I propose that since SAGE is > becoming multifaceted, moving beyond system, algebra, geometry and > exprimentation, SAGE should be rechristened as SAGE the word (and > no

[sage-devel] Re: Documentation format

2006-12-17 Thread Nick Alexander
Hi Georg, This is only somewhat on topic. I've been rewriting the scripts that generate the reference, and my understanding is that there is no 'documentation format'; there are a series of loosely followed conventions. My changes will typeset any UPCASE: heading in a somewhat sensible manner,