[sage-support] SAGE-2.8.14 released!
SAGE 2.8.14: At least the following people contributed to this release: - Michael Abshoff - Martin Albrecht - John Cremona - Alexander Dreyer - Bill Hart - David Joyner - Josh Kantor - William Stein - Carl Witty Feedback and testing by Andrzej Giniewicz and Simon King, Jaap Spies, Gregory Vanuxem and Justin Walker. Apologies to anybody I forgot. Cheers, Michael Abshoff (release chair), William Stein * Major Features, New Spkgs and Bugfixes Besides fixing the build process on OSX 10.5.1 (10.5 did work before) John Cremona also updated g0n to compile with gcc 4.2.x. This did slip through testing, which caused us to release a build so shortly after 2.8.13. - #998: segmentation fault doctesting crypto/mq/sr.py [Carl Witty] - #1244: flint-0.9-r1075.p0.spkg [Bill Hart, Michael Abshoff] - fix corner cases on Core Duo - #1246: mpfi-1.3.4-rc3.p10.spkg [Alexander Dreyer] - mpfi-1.3.4- rc3.p9 fails to build on x86_64 SuSE 10.1 - #1247: cremona-20071124.spkg [John Cremona, William Stein] - gcc 4.2.x compile fixes, Solaris build fix - #1250: multivariate polynomial factorization -- control-c to cancel out doesn't work [William Stein] - #1251: tutorial out of date [David Joyner] - #1252: cddlib-094b.p0.spkg [Michael Abshoff] - force cddlib to link against Sage's gmp - #1253: gmp-4.2.1.p12.spkg, python-2.5.1.p9.spkg, clisp-2.41.p11.spkg [Michael Abshoff] - OSX 10.5.x build fixes - #1254: revision to combinat.py [David Joyner, William Stein] - Hadamard matrices of certain types via guava, use combinat.py for permutations instead of GAP wrapper - #1257: multi_polynomial_libsingular.pyx random segfault [Carl Witty] - #1262: make check needs to depend on all [William Stein] We closed a total of 13 tickets, see http://www.sagetrac.org/sage_trac/query?status=closedmilestone=sage-2.8.14 for details. * Known Issues with 2.8.14 - cvxopt still fails to import certain functionality on OSX PPC (ticket #1222) * Upcoming Releases 2.8.15 is planned before Sage Bug Day 6 (which is on Saturday, December 1st, 2007). Major spkg candidates for 2.8.15 are - Singular 3-0-4 - PolyBoRi - ATLAS BLAS/Lapack * Coverage No changes from 2.8.13. * 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, sage-support, sage- forum or sage-newbie. You can also drop by in #sage-devel in freenode. --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@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-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: Possible bug in graph isomorphism search_tree function
Here are a couple similar graphs that go fine:
G = {0: {1: None, 6: None, 7: None, 10: None, 11: None, 12: None, 13:
None}, 1: {0: None, 6: None, 7: None, 10: None, 11: None, 12: None,
13: None, 18: None}, 2: {3: None, 4: None, 5: None, 8: None, 9: None,
14: None, 15: None, 20: None}, 3: {2: None, 4: None, 5: None, 8: None,
9: None, 14: None, 15: None, 22: None}, 4: {2: None, 3: None, 5: None,
8: None, 9: None, 14: None, 15: None, 24: None}, 5: {2: None, 3: None,
4: None, 8: None, 9: None, 14: None, 15: None, 26: None}, 6: {0: None,
1: None, 7: None, 10: None, 11: None, 12: None, 13: None, 28: None},
7: {0: None, 1: None, 6: None, 10: None, 11: None, 12: None, 13: None,
30: None}, 8: {32: None, 2: None, 3: None, 4: None, 5: None, 9: None,
14: None, 15: None}, 9: {2: None, 3: None, 4: None, 5: None, 8: None,
34: None, 14: None, 15: None}, 10: {0: None, 1: None, 36: None, 6:
None, 7: None, 11: None, 12: None, 13: None}, 11: {0: None, 1: None,
38: None, 6: None, 7: None, 10: None, 12: None, 13: None}, 12: {0:
None, 1: None, 6: None, 7: None, 40: None, 10: None, 11: None, 13:
None}, 13: {0: None, 1: None, 6: None, 7: None, 10: None, 11: None,
12: None, 42: None}, 14: {2: None, 3: None, 4: None, 5: None, 8: None,
9: None, 44: None, 15: None}, 15: {2: None, 3: None, 4: None, 5: None,
8: None, 9: None, 14: None, 46: None}, 16: {32: None, 34: None, 44:
None, 48: None, 20: None, 22: None, 24: None, 26: None}, 17: {33:
None, 35: None, 45: None, 49: None, 21: None, 23: None, 25: None, 27:
None}, 18: {32: None, 1: None, 34: None, 46: None, 50: None, 20: None,
22: None, 24: None, 26: None}, 19: {33: None, 35: None, 47: None, 51:
None, 21: None, 23: None, 25: None, 27: None}, 20: {2: None, 36: None,
38: None, 40: None, 16: None, 18: None, 52: None, 28: None, 30: None},
21: {37: None, 39: None, 41: None, 17: None, 19: None, 53: None, 29:
None, 31: None}, 22: {3: None, 36: None, 38: None, 42: None, 16: None,
18: None, 54: None, 28: None, 30: None}, 23: {37: None, 39: None, 43:
None, 17: None, 19: None, 55: None, 29: None, 31: None}, 24: {4: None,
40: None, 42: None, 16: None, 18: None, 56: None, 36: None, 28: None,
30: None}, 25: {37: None, 41: None, 43: None, 17: None, 19: None, 57:
None, 29: None, 31: None}, 26: {5: None, 38: None, 40: None, 42: None,
16: None, 18: None, 58: None, 28: None, 30: None}, 27: {39: None, 41:
None, 43: None, 17: None, 19: None, 59: None, 29: None, 31: None}, 28:
{32: None, 6: None, 44: None, 46: None, 20: None, 22: None, 24: None,
26: None, 60: None}, 29: {33: None, 45: None, 47: None, 21: None, 23:
None, 25: None, 27: None, 61: None}, 30: {34: None, 7: None, 44: None,
46: None, 20: None, 22: None, 24: None, 26: None, 62: None}, 31: {35:
None, 45: None, 47: None, 21: None, 23: None, 25: None, 27: None, 63:
None}, 32: {64: None, 36: None, 38: None, 8: None, 42: None, 16: None,
40: None, 18: None, 28: None}, 33: {65: None, 37: None, 39: None, 41:
None, 43: None, 17: None, 19: None, 29: None}, 34: {66: None, 36:
None, 38: None, 40: None, 9: None, 42: None, 16: None, 18: None, 30:
None}, 35: {67: None, 37: None, 39: None, 41: None, 43: None, 17:
None, 19: None, 31: None}, 36: {32: None, 34: None, 68: None, 10:
None, 44: None, 46: None, 20: None, 22: None, 24: None}, 37: {33:
None, 35: None, 69: None, 45: None, 47: None, 21: None, 23: None, 25:
None}, 38: {32: None, 34: None, 70: None, 11: None, 44: None, 46:
None, 20: None, 22: None, 26: None}, 39: {33: None, 35: None, 71:
None, 45: None, 47: None, 21: None, 23: None, 27: None}, 40: {32:
None, 34: None, 72: None, 44: None, 12: None, 46: None, 20: None, 24:
None, 26: None}, 41: {33: None, 35: None, 73: None, 45: None, 47:
None, 21: None, 25: None, 27: None}, 42: {32: None, 34: None, 74:
None, 44: None, 13: None, 46: None, 22: None, 24: None, 26: None}, 43:
{33: None, 35: None, 75: None, 45: None, 47: None, 23: None, 25: None,
27: None}, 44: {36: None, 38: None, 40: None, 42: None, 76: None, 14:
None, 16: None, 28: None, 30: None}, 45: {37: None, 39: None, 41:
None, 43: None, 77: None, 17: None, 29: None, 31: None}, 46: {36:
None, 38: None, 40: None, 42: None, 78: None, 15: None, 18: None, 28:
None, 30: None}, 47: {37: None, 39: None, 41: None, 43: None, 79:
None, 19: None, 29: None, 31: None}, 48: {16: None, 79: None}, 49:
{17: None, 78: None}, 50: {18: None, 77: None}, 51: {19: None, 76:
None}, 52: {75: None, 20: None}, 53: {74: None, 21: None}, 54: {73:
None, 22: None}, 55: {72: None, 23: None}, 56: {24: None, 71: None},
57: {25: None, 70: None}, 58: {26: None, 69: None}, 59: {27: None, 68:
None}, 60: {67: None, 28: None}, 61: {66: None, 29: None}, 62: {65:
None, 30: None}, 63: {64: None, 31: None}, 64: {32: None, 63: None},
65: {33: None, 62: None}, 66: {34: None, 61: None}, 67: {35: None, 60:
None}, 68: {59: None, 36: None}, 69: {58: None, 37: None}, 70: {57:
None, 38: None}, 71: {56: None, 39: None}, 72: {40: None, 55: None},
73: {41: None, 54: None}, 74: {42: None, 53: None}, 75: {43: None, 52:
None}, 76: {51: None, 44: None}, 77: {50:
[sage-support] Re: using Singular's invariant_ring
@Martin Albrecht:
- Is there a reasonable way to fix this in the interface?
Hi, the 'trivial' way to fix it, is to implement a Python function for
SinguleElement called invariant_ring which calls the Singular function,
parses the output and returns a tuple. If you call A.invariant_ring the
Singular function is only called directly if there is no Python function with
the same name.
A better - and I guess doable - approach is to track down why it fails and fix
it.
- If not: What could we do on the side of Singular to make the return
of a tuple (like return(P,S,IS)) comprehensible for the interface? I
guess return(list(P,S,IS)) would work, but i'm not sure if this
change of syntax wouldn't have nasty consequences for existing
applications.
There is a very clumsy way to pull the output of invariant_ring into
sage:
First, define A and R as above. Then say
singular.eval('matrix P,S,IS=invariant_ring(%s)'%(A.name()))
P=singular('P')
S=singular('S')
IS=singular('IS')
But definitely i do think the correct syntax should be
P,S,IS=A.invariant_ring()
and this is definitely possible either by doing what you are doing above
within a Python wrapper function or by fixing that issue.
Now, another question on the Singular interface:
In Singular, doing
matrix P,S,IS = invariant_ring(A,1);
would make Singular to additionally print information about the
progress of computations (which, in big examples, might be nice to
have).
However, when i use the Singular interface, i can not see such
informations. Where are they gone?
The information is printed but ignored because pexpect expects
Singular 'output' and ignores the rest. I am no pexpect expert so I don't
know how to fix it. It would very very useful though. Anyone else has any
idea?
Martin
--
name: Martin Albrecht
_pgp: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x8EF0DC99
_www: http://www.informatik.uni-bremen.de/~malb
_jab: [EMAIL PROTECTED]
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@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-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---
[sage-support] import sage.rings.integer fails
Hi, I started writing an external library that uses Sage and I meditatly ran into: import sage.rings.integer Traceback (most recent call last): File stdin, line 1, in module ImportError: libcsage.so: cannot open shared object file: No such file or directory import sage.rings.arith Traceback (most recent call last): File stdin, line 1, in module File /home/timothy/sage-2.8.13/local/lib/python2.5/site-packages/sage/rings/arith.py, line 14, in module import sage.misc.misc as misc File /home/timothy/sage-2.8.13/local/lib/python2.5/site-packages/sage/misc/misc.py, line 28, in module SAGE_ROOT = os.environ[SAGE_ROOT] File /home/timothy/sage-2.8.13/local/lib/python2.5/UserDict.py, line 22, in __getitem__ raise KeyError(key) KeyError: 'SAGE_ROOT' I'm using Ubuntu 7.10 64 on AMD 64X2. I'm using Sage 2.8.13 built from source upgraded to 2.8.14. I tried the Ubuntu 32 Sage binary before building from source. When I use Sage to run: [simport.py] -- from sage.rings.integer import Integer I get Unhandled SIGSEGV: A segmentation fault occured in SAGE. This probably occured because a *compiled* component of SAGE has a bug in it (typically accessing invalid memory) or is not properly wrapped with _sig_on, _sig_off. You might want to run SAGE under gdb with 'sage -gdb' to debug this. SAGE will now terminate (sorry). sage: Error running simport.py using Python In my library I won't want to have to import all of Sage just to be able to use Integer, factor, etc. --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@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-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: import sage.rings.integer fails
On Nov 25, 2007 10:30 AM, William Stein [EMAIL PROTECTED] wrote: On Nov 25, 2007 10:29 AM, Timothy Clemans [EMAIL PROTECTED] wrote: Hi, I started writing an external library that uses Sage and I meditatly ran into: import sage.rings.integer Traceback (most recent call last): File stdin, line 1, in module ImportError: libcsage.so: cannot open shared object file: No such file or directory import sage.rings.arith Traceback (most recent call last): File stdin, line 1, in module File /home/timothy/sage-2.8.13/local/lib/python2.5/site-packages/sage/rings/arith.py, line 14, in module import sage.misc.misc as misc File /home/timothy/sage-2.8.13/local/lib/python2.5/site-packages/sage/misc/misc.py, line 28, in module SAGE_ROOT = os.environ[SAGE_ROOT] File /home/timothy/sage-2.8.13/local/lib/python2.5/UserDict.py, line 22, in __getitem__ raise KeyError(key) KeyError: 'SAGE_ROOT' You can't use anything from the Sage library if the environment isn't setup. If you use sage -python or sage -ipython, then it will start Sage's Python or IPython with the environment setup correctly. William I'm using Ubuntu 7.10 64 on AMD 64X2. I'm using Sage 2.8.13 built from source upgraded to 2.8.14. I tried the Ubuntu 32 Sage binary before building from source. When I use Sage to run: [simport.py] -- from sage.rings.integer import Integer I get Unhandled SIGSEGV: A segmentation fault occured in SAGE. This probably occured because a *compiled* component of SAGE has a bug in it (typically accessing invalid memory) or is not properly wrapped with _sig_on, _sig_off. You might want to run SAGE under gdb with 'sage -gdb' to debug this. SAGE will now terminate (sorry). sage: Error running simport.py using Python In my library I won't want to have to import all of Sage just to be able to use Integer, factor, etc. You *have* to do import sage.all before doing any other imports of mathematical things from the sage library. Full stop. It should not and cannot work otherwise. -- William -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@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-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: Possible bug in graph isomorphism search_tree function
Okay, I guess the profiler is only profiling Python calls, so it's not so good to figure out what's going on. There are some linux tools that may help with this. I will look into this and post back in a while (maybe 1 week) when I have something. Thank you for reporting this important example. -- Robert Miller --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@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-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: using Singular's invariant_ring
Hi David,
On Nov 24, 10:38 pm, David Joyner [EMAIL PROTECTED] wrote:
The commands at
http://www.singular.uni-kl.de/Manual/latest/sing_1083.htm#SEC1142
are a good example to start.
In my previous post, i explained how one might use invariant_ring (for
getting a Hironaka decomposition) or invariant_algebra_reynolds (for
getting minimal sub-algebra generators).
For completeness, i explain here what one may do in the special case
of a permutation group, and would like to combine it with another
question on the correct use of the Singular interface.
Let IR be the invariant ring of a non-modular representation of a
permutation group. We will compute a minimal set of sub-algebra
generators for IR.
A permutation group is given by a list of generators, where each
generator is presented by a list of disjoint cycles, where each cycle
is a list of integers. So, for the natural action of the cyclic group
of order 9 in characteristic 2, you would write
sage: singular.LIB(finvar.lib)
sage: R=singular.ring(2,'(x(1..9))','dp')
sage:
K=singular.list((singular.list('1,2,3,4,5,6,7,8,9').list()).list())
And then, you get a minimal set of generators by
sage: IR=K.invariant_algebra_perm()
In this innocent-looking example, there are minimally 119 (!)
generators, so IR is a 1x119 Singular matrix.
Here is my question about the use of the Singular interface. Above, i
define
sage:
K=singular.list((singular.list('1,2,3,4,5,6,7,8,9').list()).list())
which is not exactly elegant. Is there a better way to do in sage what
in Singular was
def K = list(list(list(1,2,3,4,5,6,7,8,9)))
?
Yours
Simon
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@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-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---
[sage-support] Re: using Singular's invariant_ring
On Nov 25, 2007 3:27 AM, Martin Albrecht [EMAIL PROTECTED] wrote:
@Martin Albrecht:
- Is there a reasonable way to fix this in the interface?
Hi, the 'trivial' way to fix it, is to implement a Python function for
SinguleElement called invariant_ring which calls the Singular function,
parses the output and returns a tuple. If you call A.invariant_ring the
Singular function is only called directly if there is no Python function with
the same name.
A better - and I guess doable - approach is to track down why it fails and fix
it.
- If not: What could we do on the side of Singular to make the return
of a tuple (like return(P,S,IS)) comprehensible for the interface? I
guess return(list(P,S,IS)) would work, but i'm not sure if this
change of syntax wouldn't have nasty consequences for existing
applications.
There is a very clumsy way to pull the output of invariant_ring into
sage:
First, define A and R as above. Then say
singular.eval('matrix P,S,IS=invariant_ring(%s)'%(A.name()))
P=singular('P')
S=singular('S')
IS=singular('IS')
But definitely i do think the correct syntax should be
P,S,IS=A.invariant_ring()
and this is definitely possible either by doing what you are doing above
within a Python wrapper function or by fixing that issue.
Now, another question on the Singular interface:
In Singular, doing
matrix P,S,IS = invariant_ring(A,1);
would make Singular to additionally print information about the
progress of computations (which, in big examples, might be nice to
have).
However, when i use the Singular interface, i can not see such
informations. Where are they gone?
The information is printed but ignored because pexpect expects
Singular 'output' and ignores the rest. I am no pexpect expert so I don't
know how to fix it. It would very very useful though. Anyone else has any
idea?
I think this would be possible to implement, by modifying
interfaces/singular.py.
Please open a trac ticket. It's easiest if we just have it print out
the result of
all the verbose output, rather than all of it along the way as it is
output by singular,
though the latter would also be possible. With pseudo-tty's it is
possible to do
anything you could really imagine doing by hand while physically using
a terminal
to interact with singular. Anything.
-- William
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@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-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---
[sage-support] Re: using Singular's invariant_ring
On Nov 25, 2007 4:29 PM, William Stein [EMAIL PROTECTED] wrote:
On Nov 25, 2007 3:27 AM, Martin Albrecht [EMAIL PROTECTED] wrote:
@Martin Albrecht:
- Is there a reasonable way to fix this in the interface?
Hi, the 'trivial' way to fix it, is to implement a Python function for
SinguleElement called invariant_ring which calls the Singular function,
parses the output and returns a tuple. If you call A.invariant_ring the
Singular function is only called directly if there is no Python function
with
the same name.
A better - and I guess doable - approach is to track down why it fails and
fix
it.
- If not: What could we do on the side of Singular to make the return
of a tuple (like return(P,S,IS)) comprehensible for the interface? I
guess return(list(P,S,IS)) would work, but i'm not sure if this
change of syntax wouldn't have nasty consequences for existing
applications.
There is a very clumsy way to pull the output of invariant_ring into
sage:
First, define A and R as above. Then say
singular.eval('matrix P,S,IS=invariant_ring(%s)'%(A.name()))
P=singular('P')
S=singular('S')
IS=singular('IS')
But definitely i do think the correct syntax should be
P,S,IS=A.invariant_ring()
and this is definitely possible either by doing what you are doing above
within a Python wrapper function or by fixing that issue.
Now, another question on the Singular interface:
In Singular, doing
matrix P,S,IS = invariant_ring(A,1);
would make Singular to additionally print information about the
progress of computations (which, in big examples, might be nice to
have).
However, when i use the Singular interface, i can not see such
informations. Where are they gone?
The information is printed but ignored because pexpect expects
Singular 'output' and ignores the rest. I am no pexpect expert so I don't
know how to fix it. It would very very useful though. Anyone else has any
idea?
I think this would be possible to implement, by modifying
interfaces/singular.py.
Please open a trac ticket. It's easiest if we just have it print out
Done:
http://sagetrac.org/sage_trac/ticket/1274
I'll open one up regarding the original question (about invariant rings)
when I've thought about it more. Hopefully Tuesday sometime.
the result of
all the verbose output, rather than all of it along the way as it is
output by singular,
though the latter would also be possible. With pseudo-tty's it is
possible to do
anything you could really imagine doing by hand while physically using
a terminal
to interact with singular. Anything.
-- William
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@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-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~--~~~~--~~--~--~---
[sage-support] Re: SAGE-2.8.14 released!
On Nov 25, 2007, at 24:24 , mabshoff wrote: SAGE 2.8.14: At least the following people contributed to this release: Built and tested (make test) successfully: Mac OS X, 10.4.11 (Dual Quad Core Xeon, -j6): real61m34.078s user47m3.121s sys 24m32.670s All tests passed! Total time for all tests: 2268.1 seconds Mac OS X, 10.5.1 (Core Duo -j2): real85m41.833s user71m35.291s sys 16m17.120s All tests passed! Total time for all tests: 2618.4 seconds -- Justin C. Walker, Curmudgeon-At-Large Director Institute for the Enhancement of the Director's Income Weaseling out of things is what separates us from the animals. Well, except the weasel. - Homer J Simpson --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@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-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: trac
On Nov 25, 2007 8:27 PM, Dennis Stein [EMAIL PROTECTED] wrote: Type trac() Warning: found no users in realm: localhost After opening Trac at: http://localhost:1 Browser displays: Available Projects Open Kitchen Click on link and go to http://localhost:1/sage_trac gives this error: Yuck. I guess it just doesn't work... Thanks for letting me know. One probably easy way to fix this would be for you to build all of Sage yourself from source! It's only 5 million lines. Actually it's very very easy to do. Just download sage-2.8.14.tar from here: http://sagemath.org/dist/src/ then type into Terminal: $ tar xvf sage-2.8.14.tar $ cd sage-2.8.14 $ make then wait 1 hour. The contents of the resulting directory will include a program sage, and typing $ ./sage will start it. Then install trac again, and try it out. It just worked for me. File /Applications/sage-2.8.13-osx10.5-i386-Darwin/local/lib/python/locale.py, line 494, in getpreferredencoding import _locale ImportError: No module named _locale On Nov 25, 2007 3:49 PM, William Stein [EMAIL PROTECTED] wrote: On Nov 25, 2007 3:39 PM, Dennis Stein [EMAIL PROTECTED] wrote: At the sage prompt, I type: sage: trac( and it gives me this: sage: trac() : I suppose it might be working! = At the command prompt, I type: dstein$ ./sage trac python: can't open file 'trac': [Errno 2] No such file or directory sage: Error running trac using Python That doesn't seem to work. -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@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-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
