[sage-devel] Re: Mathematica doctest

Hi Felix, I was reading up about some other stuff - http://www.gap-system.org/ForumArchive/Egner.1/Sebastia.1/%5BMathema.1/1.html which reminded me about your comments about the new line characters. Can this be fixed by following the example above and using the option PageWidth -> Infinity? Simon

[sage-devel] Re: Groups in Sage, libgap

Hi Mike, On 14 March 2010 02:12, Mike OS wrote: > I had concerns that posting on gap-from and gap-support > might make the discussion to diffused and harder to keep track of. > I dont have experience with discussion groups.  What would you > suggest? OK, we'll see, so far indeed it's a bit prema

Re: [sage-devel] GSoC 2010 project idea: adding functionality to PYCA

On Fri, 12 Mar 2010 at 11:04AM -0800, Kazuo Thow wrote: > It came to my attention a little while ago that Sage is applying to be > a Google Summer of Code mentoring organization, and soon after that I > discovered PYCA ( http://code.google.com/p/cellular-automata-sage-toolkit/ > ), a cellular autom

Re: [debian-sage] Re: [sage-devel] Re: Debian package...

Alex Ghitza wrote: Maybe we should just take whatever version of Sage is in Ubuntu right now and patch it so that running sage simply exits with something like ** THIS VERSION OF SAGE IS RIDICULOUSLY OUT-OF-DATE! Please downlo

Re: [debian-sage] Re: [sage-devel] Re: Debian package...

On Mar 13, 2010, at 5:48 PM, Tim Abbott wrote: On Sun, 14 Mar 2010, Alex Ghitza wrote: However, they did say that given the circumstances, it might be possible to push through a major update to the package to Karmic when once one is available. So I think this leaves us at "we need to upda

Re: [debian-sage] Re: [sage-devel] Re: Debian package...

On Sun, 14 Mar 2010, Alex Ghitza wrote: > > However, they did say that given the circumstances, it might be possible > > to push through a major update to the package to Karmic when once one is > > available. > > > > So I think this leaves us at "we need to update the package". Sigh. > > Mayb

Re: [debian-sage] Re: [sage-devel] Re: Debian package...

Hi Tim, Thanks for looking into this! On Sat, 13 Mar 2010 20:02:18 -0500 (EST), Tim Abbott wrote: > The answer I got on this is that there is no procedure for removing a > package from a stable release -- Ubuntu doesn't do that kind of thing. That's pretty hilarious. > However, they did say

Re: [sage-devel] Re: [sage-combinat-devel] FAQ and Thematic Tutorials for standard documentation

Hi folks, On Sun, Mar 14, 2010 at 11:18 AM, Minh Nguyen wrote: > See ticket #8533 > > http://trac.sagemath.org/sage_trac/ticket/8533 I have provided another implementation with the help of John Palmieri. See the second patch at #8533. The attachment "trac_8533-browse-doc-take2.patch" is anoth

Re: [sage-devel] Re: Debian package...

I suggested somewhere that such a package should just download a binary installation of sage. Even Debian has packages of this type. Dmitrii On Mar 14, 9:02 am, Tim Abbott wrote: > On Fri, 12 Mar 2010, Tim Abbott wrote: > > As I mentioned on the bug report opened today at > >

Re: [debian-sage] Re: [sage-devel] Re: Debian package...

On Fri, 12 Mar 2010, Tim Abbott wrote: > As I mentioned on the bug report opened today at > , I'm talking to > a member of the Ubuntu stable release update team who I know to see what > the procedure would be for getting the package remov

Re: syntax support for _sig_on / _sig_off in cython (Re: [sage-devel] Re: Memory leak)

On Mar 13, 2010, at 4:04 PM, Gonzalo Tornaria wrote: On Sat, Mar 13, 2010 at 2:30 PM, Robert Bradshaw wrote: On Mar 13, 2010, at 5:29 AM, Nicolas M. Thiery wrote: def bla(...): with sig_on: if ... raise ... elif ... return ... This is exactly

Re: [sage-devel] Re: [sage-combinat-devel] FAQ and Thematic Tutorials for standard documentation

Hi John, On Sun, Mar 14, 2010 at 7:00 AM, John H Palmieri wrote: > You could use the command "browse_sage_doc" defined in > "sage.misc.sagedoc": this allows you to open up documentation from > within Sage. More precisely, add the documents you want to the class > "_sage_doc". That is it! Tha

syntax support for _sig_on / _sig_off in cython (Re: [sage-devel] Re: Memory leak)

On Sat, Mar 13, 2010 at 2:30 PM, Robert Bradshaw wrote: > On Mar 13, 2010, at 5:29 AM, Nicolas M. Thiery wrote: >> >>  def bla(...): >>      with sig_on: >>        if ... >>           raise ... >>        elif ... >>           return >>        ... This is exactly the required semantics. I didn't k

[sage-devel] Success / Failures of 'optional' packages on Solaris.

I tried to install some optional packages and immediately hit a snag due to a GNUism, where 'grep' is called with the '-o' option. John Palmieri thought the -o was unneeded, and that is indeed the case. If someone wants to review that patch (only removal of two characters), it is here. http://

Re: [sage-devel] testing on t2

On Fri, Mar 12, 2010 at 10:03 PM, Minh Nguyen wrote: > ... > if [ $UNAME = "Darwin" ]; then >    OPT="Rp" > else >    OPT="ra" > fi > > I'm referring to the option "a", which is passed to cp later on in > that script. With sage-bdist as is, I can't wrap up my build. But if I > remove the option "a

[sage-devel] Re: Sage 4.3.4.alpha1 released!

Mike Hansen wrote: Hello all, This release should fix many of the outstanding issues on Solaris as well as some more of the combinatorics code from Sage Days 20. Source tarball: http://sage.math.washington.edu/home/release/sage-4.3.4.alpha1/sage-4.3.4.alpha1.tar Binary for sage.math: http://

[sage-devel] Re: [sage-combinat-devel] FAQ and Thematic Tutorials for standard documentation

On Mar 12, 3:23 pm, Minh Nguyen wrote: > Hi Nicolas, > > On Sat, Mar 13, 2010 at 8:51 AM, Nicolas M. Thiery > > wrote: > > > > > For the first one, __init__ import's primer. For the second, I set > > the __doc__ entry. > > Yes, that trick of yours is certainly better than hacking sage/all.py. >

Re: [sage-devel] Re: Memory leak

On Mar 13, 2010, at 5:29 AM, Nicolas M. Thiery wrote: On Thu, Mar 11, 2010 at 12:07:16AM -0500, Gonzalo Tornaria wrote: What may actually be nice is to have some kind of support in cython to declare we want signals enabled for a whole function (something like a decorator or attribute). Cyth

Re: [sage-devel] Re: [sage-combinat-devel] FAQ and Thematic Tutorials for standard documentation

On Sat, Mar 13, 2010 at 10:23:14AM +1100, Minh Nguyen wrote: > Yes, that trick of yours is certainly better than hacking sage/all.py. > One problem down, one to go. I still don't know how to put a tutorial > under the Sage library and at the same time have it listed in the > category "Thematic Tuto

Re: [sage-devel] Re: Should there be some *good* examples on notebook?

On Wed, Feb 24, 2010 at 09:16:02AM +, John Cremona wrote: > ...and then we would want some way of testing that all the "good" > worksheets all still work with each new release? Shouldn't those "good" worksheets simply be the "Thematic Tutorials" that Minh is currently organizing? All in all, t

Re: [sage-devel] Re: Small bug in trac e-mail report

Hi Craig, > > The author should be nthiery and not newvalueoldvalue. You can find other > > instance of this bug in eg. in [2],[3]. Is it known ? Should it be reported > > somewhere ? Should I open a ticket about it ? Any idea where it is coming > > from ? Is is sufficiently harmless s

[sage-devel] Re: Small bug in trac e-mail report

> The author should be nthiery and not newvalueoldvalue. You can find other > instance of this bug in eg. in [2],[3]. Is it known ? Should it be reported > somewhere ? Should I open a ticket about it ? Any idea where it is coming > from ? Is is sufficiently harmless so that it should be ignored ? >

Re: [sage-devel] Re: Memory leak

On Thu, Mar 11, 2010 at 12:07:16AM -0500, Gonzalo Tornaria wrote: > What may actually be nice is to have some kind of support in cython to > declare we want signals enabled for a whole function (something like a > decorator or attribute). Cython would then add the calls to every > entry and exit po

Re: [sage-devel] Re: conjugacy_class(es)_representatives

On Sat, Mar 13, 2010 at 11:13:13AM +0100, Florent hivert wrote: > > We probably do not have to worry much about that, since the issue will > > most likely disappear with Javier's work on conjugacy classes. If I > > remember well, the plan is to be able to do, for any (finite) group G: > > > >

Re: [sage-devel] Re: testing on t2

Dima Pasechnik wrote: Can't one just make a private copy of a SAGE_ROOT of an already built installation? (The only requirement is that everything in SAGE_ROOT is world- readable.) Simply copying it will result in a massive expansion of disk space as the links are not copied properly. As Minh

Re: [sage-devel] testing on t2

Minh Nguyen wrote: Hi Alex, On Sat, Mar 13, 2010 at 10:36 AM, Alex Ghitza wrote: Building Sage on t2 takes a long time. It would be great to have a t2.math binary available for each alpha/rc/final release of Sage, which anyone can just grab and untar and start testing on *right away*. Bu

[sage-devel] Re: testing on t2

Can't one just make a private copy of a SAGE_ROOT of an already built installation? (The only requirement is that everything in SAGE_ROOT is world- readable.) Dima On Mar 13, 7:36 am, Alex Ghitza wrote: > Hi, > > (This email got a bit long.  See EXECUTIVE SUMMARY below for the > conclusion.) > >

[sage-devel] Small bug in trac e-mail report

Hi there, There is a small bug in trac's automatic report by e-mails. On sage-combinat-comm...@googlegroups.com we just receive the following e-mail from trac (see [1] below) > #8500: Add the set of TransitiveGroups > -+---

Re: [sage-devel] Re: conjugacy_class(es)_representatives

Hi Nicolas, > On Fri, Mar 12, 2010 at 11:16:08AM -0800, Nick Alexander wrote: > > On 12-Mar-10, at 10:42 AM, Rob Beezer wrote: > > >The distinction is one group is a matrix group and the other is a > > >permutation group. > > > > > >sage/groups/matrix_gps/matrix_group.py > > >sage/groups/per

Re: [sage-devel] Re: Sage 4.3.4.alpha1 successfully builds on SPARC Solaris 10 (t2.math)

John H Palmieri wrote: On Mar 10, 3:09 pm, Minh Nguyen wrote: Hi folks, Yes, you heard right. Sage 4.3.4.alpha1 now builds on t2.math thanks to the persistent hard work of David Kirkby. I just tried to build this version of Sage on two of the Skynet machines running Solaris, unsuccessfully,

Re: [sage-devel] Re: Mathematica doctest

On Mar 12, 2010, at 7:01 PM, Felix Lawrence wrote: On Mar 12, 3:17 pm, Jason Grout wrote: So the Mathematica *input* syntax is closer to the sage *input* syntax, while the mathematica full form (i.e., the internal tree of operations) is closer to the sage tree of operations. That makes a

Re: [sage-devel] Re: conjugacy_class(es)_representatives

Hi! On Fri, Mar 12, 2010 at 11:16:08AM -0800, Nick Alexander wrote: > On 12-Mar-10, at 10:42 AM, Rob Beezer wrote: > >The distinction is one group is a matrix group and the other is a > >permutation group. > > > >sage/groups/matrix_gps/matrix_group.py > >sage/groups/perm_gps/permgroup.py >