[sage-devel] Congratulations to IPython

2013-03-23 Thread David Roe
IPython has won the 2012 Free Software foundation award for the Advancement of Free Software ( http://www.fsf.org/news/2012-free-software-award-winners-announced-2). Well deserved! David -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscri

[sage-devel] Re: [sage-release] Re: sage-5.9.beta0 released

2013-03-23 Thread Volker Braun
Might be because of the SIGCHLD handler issue in libgap that has been waiting for a review at http://trac.sagemath.org/14039. See also http://trac.sagemath.org/14323 for a more temporary fix. Though if thats the root cause then I don't understand why it would not be triggered for everyone...

[sage-devel] Re: sagenb.org is down

2013-03-23 Thread Jason Grout
On 3/23/13 10:55 AM, gerald wenzel wrote: sagenb.org is returning 503 errors: 503 Service Unavailable No server is available to handle this request. You're right. Thanks. I'm restarting it now. Jason -- You received this message because you are subscribed to the Google Groups "sag

[sage-devel] sagenb.org is down

2013-03-23 Thread gerald wenzel
sagenb.org is returning 503 errors: 503 Service Unavailable No server is available to handle this request. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-d

[sage-devel] Re: [sage-release] Re: sage-5.9.beta0 released

2013-03-23 Thread John Cremona
While I still think there is a serious issue here, friends will be delighted to hear that I was able to get onto the server in question and kill the two offending ecl processes. I do not know why, but while it was impossible to login from off campus, I could login to a different machine on the uni

[sage-devel] Re: [sage-release] Re: sage-5.9.beta0 released

2013-03-23 Thread John Cremona
On 19 March 2013 15:16, John Cremona wrote: > Exactly the same happened to me: 2 rogue ecl processes consuming lots > of RAM. This is on ubuntu, same set up worked fine with 5.8 at the > same time. This report provoked almost no reaction in a thread dominated by vital discussion of colour scheme

[sage-devel] new M4RI(E) SPKGs need review

2013-03-23 Thread Martin Albrecht
Hi, I've released new versions of M4RI and M4RIE and I'd appreciate if someone could take the time to review the relevant tickets to get these updates into Sage: M4RI:http://trac.sagemath.org/sage_trac/ticket/14335 M4RIE: http://trac.sagemath.org/sage_trac/ticket/14336 # What's new? # ##

Re: [sage-devel] Re: Re: Re: Re: Re: a problem in the new permutation groups code (and a solution ?)

2013-03-23 Thread Volker Braun
On Saturday, March 23, 2013 1:43:05 PM UTC+1, Dima Pasechnik wrote: > Now, if 1, 2, and (1,2) are in your domain, is (2,(1,2)) a tuple? > According to the "minimum depth" rule to guess the default action, it is. > And how many different meanings does ((2,(1,2)),((2,(1,2))) have? > There is

Re: [sage-devel] Re: a problem in the new permutation groups code (and a solution ?)

2013-03-23 Thread Nathann Cohen
> Say, you have 1, 2, (1,2), (2,(1,2)), and perhaps other stuff in the domain. > How many different meanings does "the orbit of ((2,(1,2)),((2,(1,2)))" have? > How can you guess the "right" action for it? Dima it's getting boring. Let's say that I do not try to guess anything if that's a problem,

[sage-devel] Re: a problem in the new permutation groups code (and a solution ?)

2013-03-23 Thread Dima Pasechnik
On 2013-03-23, Volker Braun wrote: > --=_Part_1329_18134862.1364030357521 > Content-Type: text/plain; charset=ISO-8859-1 > > We are talking about guessing the action once and for all for a given > input. You are talking about guessing the action each time a group element > acts in the orbit.

Re: [sage-devel] Re: Re: Re: Re: Re: a problem in the new permutation groups code (and a solution ?)

2013-03-23 Thread Volker Braun
We are talking about guessing the action once and for all for a given input. You are talking about guessing the action each time a group element acts in the orbit. I agree that the latter is not consistently doable. But it is possible to guess the action in the beginning of the orbit computatio

Re: [sage-combinat-devel] Re: [sage-devel] Re: Re: Re: Re: Re: a problem in the new permutation groups code (and a solution ?)

2013-03-23 Thread Nathann Cohen
> no, the 3rd element is computed using a different meaning of (1,2) than > the one used to compute the 2nd one. > If you used the same meaning for the 2nd as the one for the 3rd, your > 2nd would be (1,1). Then how is your input of type "Tuple of Tuple", sir ? > OK, great, so (1,2) is not an ele

[sage-devel] Re: [sage-combinat-devel] Re: Adding data in patch

2013-03-23 Thread Volker Braun
Just make the source repository public and cut releases for p_group_cohomology from that. Even without the change to git I think that this is a much better model than putting a repo in a tarball and not have it web accessible. Since we are already planning on hosting our own git repo for Sage i

Re: [sage-combinat-devel] Re: [sage-devel] Re: Re: Re: a problem in the new permutation groups code (and a solution ?)

2013-03-23 Thread Nathann Cohen
> Even if you manage to answer the question above satisfactory, > I still hold that it's not acceptable in the first place to have such > design, > forcing one to jump through hoops for no good reason, in an extendable > system like Sage. This design is CORRECT Dima, if you don't believe so just g

Re: [sage-devel] Re: [sage-combinat-devel] Re: Re: Re: Re: a problem in the new permutation groups code (and a solution ?)

2013-03-23 Thread Nathann Cohen
Helloo ! > In more detail: one writes a function that can do GAP's OnTuplesTuples action, > without even any action guessing involved (this is trivial code, > right, we have things like this on our ticket?), and asks it to do the > orbit of the tuple of tuples ((1,2),(1,2)). The outcome The o

[sage-devel] Re: [sage-combinat-devel] Re: Adding data in patch

2013-03-23 Thread Simon King
Hi Keshav, hi all, On 2013-03-23, Keshav Kini wrote: >> Hence, "we don't want to pull in upstream source as well" simply does not >> apply. The question is: Do we want to *remove* source, just because Sage >> is the only project that has this code? > > I would say that yes, we do want to remove i