[sage-devel] Re: New doctest continuation ....:

2013-06-20 Thread Simon King
Hi! On 2013-06-20, kcrisman wrote: >> the matroids code (#7477) has plenty of examples. Until now I wasn't even >> aware of the existence of live documentation... but it's incredibly useful! >> > > It is SO useful!!! I've never heard of it either. Can you briefly explain what it is? Best reg

Re: [sage-devel] Broken link?

2013-06-20 Thread Jeroen Demeyer
On 06/21/2013 02:02 AM, Minh Nguyen wrote: I don't think the link is broken. Perhaps we need to wait until most mirrors are up to date with Sage 5.10. Still broken... -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this grou

Re: [sage-devel] Problem building sage-5.11.beta2

2013-06-20 Thread Jeroen Demeyer
On 06/20/2013 07:51 PM, Stephen Montgomery-Smith wrote: It is easy to provide a working patch, but why was this compilation done with -Werror set? Good question, it's only this one file which is compiled with -Werror. I suggest you file an upstream bug to PPL. -- You received this message beca

Re: [sage-devel] Re: Sqrt simplification

2013-06-20 Thread rjf
On Thursday, June 20, 2013 1:04:51 AM UTC-7, Eric Gourgoulhon wrote: > > Thanks for your explanation. So it is clear that radcan ignore assumptions. > As already mentioned by kcrisman, radcan does not take into account the > option variable radexpand, which, if set to 'true' (and domain to 'real

[sage-devel] Re: New doctest continuation ....:

2013-06-20 Thread leif
leif wrote: Keshav Kini wrote: Stefan writes: I'd ask for p[6:], that's the expected use and consistent with the previous line which tests for '... ' (note the space). I agree with that - I was just miming the .lstrip() after 'sage:' found in previous lines. I'll fix it. Cf. #10458 ... :-

[sage-devel] Re: New doctest continuation ....:

2013-06-20 Thread leif
Keshav Kini wrote: Stefan writes: I'd ask for p[6:], that's the expected use and consistent with the previous line which tests for '... ' (note the space). I agree with that - I was just miming the .lstrip() after 'sage:' found in previous lines. I'll fix it. Cf. #10458 ... :-) -leif -

Re: [sage-devel] Broken link?

2013-06-20 Thread Minh Nguyen
Hi Jan, On Fri, Jun 21, 2013 at 2:00 AM, Jan Groenewald wrote: > http://sagemath.org/download-linux.html says > > You can see the full list of mirror servers here. which goes to > > http://sagemath.org/mirrors.html which says > > error: please contact site admin. I don't think the link is broken

[sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences

2013-06-20 Thread leif
kcrisman wrote: The shrillness level has gotten a little higher than really necessary, certainly than customary on this list. We haven't seen illustrations of the effect of the @bushy_tail decorators yet... :P -leif -- () The ASCII Ribbon Campaign /\ Help Cure HTML E-Mail -- You receive

[sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences

2013-06-20 Thread leif
Volker Braun wrote: Right now there is not really anything, thats a question of what the find_stat roadmap is. But I don't see a need for that unless there is any need for it. +1 -leif -- () The ASCII Ribbon Campaign /\ Help Cure HTML E-Mail -- You received this message because you are s

[sage-devel] Re: New doctest continuation ....:

2013-06-20 Thread Keshav Kini
Keshav Kini writes: > Keshav Kini writes: >> Stefan writes: >> >>> I'd ask for p[6:], that's the expected use and consistent with the previous >>> line which tests for '... ' (note the space). >> >> I agree with that - I was just miming the .lstrip() after 'sage:' found >> in previous lines. I'

[sage-devel] Re: New doctest continuation ....:

2013-06-20 Thread Keshav Kini
Keshav Kini writes: > Stefan writes: > >> I'd ask for p[6:], that's the expected use and consistent with the previous >> line which tests for '... ' (note the space). > > I agree with that - I was just miming the .lstrip() after 'sage:' found > in previous lines. I'll fix it. OK, pushed. How mu

[sage-devel] Re: New doctest continuation ....:

2013-06-20 Thread Keshav Kini
Stefan writes: > I'd ask for p[6:], that's the expected use and consistent with the previous > line which tests for '... ' (note the space). I agree with that - I was just miming the .lstrip() after 'sage:' found in previous lines. I'll fix it. -Keshav -- You received this message because yo

[sage-devel] Re: New doctest continuation ....:

2013-06-20 Thread Stefan
I'd ask for p[6:], that's the expected use and consistent with the previous line which tests for '... ' (note the space). --Stefan. -- 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,

[sage-devel] Re: New doctest continuation ....:

2013-06-20 Thread kcrisman
Don't strip, line continuations are often indented. > > Correct, I just confirmed that breaks things. Keshav, do you want to do > the same diff without the lstrip, or should I submit a pull request? > I should point out that I confirmed this makes things not break :) -- You received this me

[sage-devel] Re: New doctest continuation ....:

2013-06-20 Thread kcrisman
On Thursday, June 20, 2013 4:26:00 PM UTC-4, kcrisman wrote: > > > Don't strip, line continuations are often indented. > >> >> Correct, I just confirmed that breaks things. Keshav, do you want to do >> the same diff without the lstrip, or should I submit a pull request? >> > > I should point ou

[sage-devel] Re: New doctest continuation ....:

2013-06-20 Thread kcrisman
On Thursday, June 20, 2013 4:14:24 PM UTC-4, Stefan wrote: > > Don't strip, line continuations are often indented. Correct, I just confirmed that breaks things. Keshav, do you want to do the same diff without the lstrip, or should I submit a pull request? -- You received this message becaus

[sage-devel] Re: New doctest continuation ....:

2013-06-20 Thread kcrisman
On Thursday, June 20, 2013 3:51:01 PM UTC-4, Keshav Kini wrote: > > Stefan > writes: > > > The fix should be adding two lines after line 374 of > > > > > https://github.com/sagemath/sagenb/blob/master/sagenb/notebook/docHTMLProcessor.py > > > > > I don't have time to get acquainted with No

[sage-devel] Re: New doctest continuation ....:

2013-06-20 Thread Stefan
Don't strip, line continuations are often indented. -- 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-devel+unsubscr...@googlegroups.com. To post to this group,

[sage-devel] Re: New doctest continuation ....:

2013-06-20 Thread Keshav Kini
Stefan writes: > The fix should be adding two lines after line 374 of > > https://github.com/sagemath/sagenb/blob/master/sagenb/notebook/docHTMLProcessor.py > > I don't have time to get acquainted with Notebook development right now, or > I'd fix it myself... Like this, I imagine? https://gith

[sage-devel] Re: New doctest continuation ....:

2013-06-20 Thread Stefan
The fix should be adding two lines after line 374 of https://github.com/sagemath/sagenb/blob/master/sagenb/notebook/docHTMLProcessor.py I don't have time to get acquainted with Notebook development right now, or I'd fix it myself... -- You received this message because you are subscribed to th

[sage-devel] Re: New doctest continuation ....:

2013-06-20 Thread kcrisman
> > > Confirmed; > Thanks for confirming. > the matroids code (#7477) has plenty of examples. Until now I wasn't even > aware of the existence of live documentation... but it's incredibly useful! > It is SO useful!!! -- You received this message because you are subscribed to the Goo

[sage-devel] Re: New doctest continuation ....:

2013-06-20 Thread Stefan
> I believe that this style of continuation breaks the live documentation. > I couldn't easily find any non-underscore methods (which of course don't > show up in the reference manual) but while working on #13381 I discovered > this. So it would be very, very good to fix this before requirin

[sage-devel] Re: New doctest continuation ....:

2013-06-20 Thread kcrisman
On Wednesday, May 8, 2013 5:58:13 AM UTC-4, Jeroen Demeyer wrote: > > The new doctesting framework allows doctests with continuation to be > written like > > sage: > : > : > > instead of the old > > I believe that this style of continuation breaks the live documentation. I couldn

Re: [sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences

2013-06-20 Thread Volker Braun
On Thursday, June 20, 2013 9:34:48 AM UTC-7, Nathann Cohen wrote: > More seriously, wouldn't changing the decorator to something that > registers the method and not change it do the trick > There decorator performs two functions currently: 1) label the method as a combinatorial map 2) transfor

[sage-devel] Problem building sage-5.11.beta2

2013-06-20 Thread Stephen Montgomery-Smith
This is in the build of ppl-1.0.p0, on FreeBSD-8.2, using its gcc46 compiler. The relevant lines seem to be: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../interfaces/C -I/usr/home/stephen/sage-devel/work/sage-5.11.beta2/local/include -pedantic -std=gnu89 -Werror -g -O2 -frounding-math -pipe -Wl,-rpath

[sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences

2013-06-20 Thread kcrisman
Or other beverage as appropriate :) The shrillness level has gotten a >> little higher than really necessary, certainly than customary on this list. >> > > Does your comment apply in particular to my last post? I certainly did > not want to be shrill - sorry if that was your impression when r

Re: [sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences

2013-06-20 Thread Nathann Cohen
Hello ! > Please propose a mechanism that > * Only occupies a single line of code I propose that we immediately strip Sage's sources of all its `\n` > * Outside of the method body, so it is separated from the actual implementation I propose that we shuffle the lines of each file, and keep i

Re: [sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences

2013-06-20 Thread Nathann Cohen
Hellooo !! > Thanks Nathann for starting the discussion (though I sometimes think that > being a little less aggressive wouldn't hurt). Yes, sorry about that. But it takes a lifetime to get people to admit the most elementary things. I mean, my first message contained two line

[sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences

2013-06-20 Thread Christian Stump
On Thursday, June 20, 2013 5:59:55 PM UTC+2, kcrisman wrote: > Or other beverage as appropriate :) The shrillness level has gotten a > little higher than really necessary, certainly than customary on this list. > Does your comment apply in particular to my last post? I certainly did not want

[sage-devel] Broken link?

2013-06-20 Thread Jan Groenewald
http://sagemath.org/download-linux.html says You can see the full list of mirror servers here. which goes to http://sagemath.org/mirrors.html which says error: please contact site admin . Regards, Jan -- .~. /V\ Jan Gr

[sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences

2013-06-20 Thread kcrisman
> > Having said that, the gals and guys responsible for #14734 and #14732 are > at > Sagedays 49 now, go and buy them the necessary amount of beer to have > all this sorted out :-) > Or other beverage as appropriate :) The shrillness level has gotten a little higher than really necessary, c

[sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences

2013-06-20 Thread Christian Stump
Dear all, Thanks Nathann for starting the discussion (though I sometimes think that being a little less aggressive wouldn't hurt). Let me start with what the positive sides of a combinatorial_map decorator are for us (and I think several of the combinat people do agree here): - we obtain a bet

Re: [sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences

2013-06-20 Thread Volker Braun
On Thursday, June 20, 2013 8:33:47 AM UTC-7, Nathann Cohen wrote: > WHY should this > thing be implemented like that when there are non-intrusive ways to > make find_stat work ?" Please propose a mechanism that * Only occupies a single line of code * Outside of the method body, so it is s

Re: [sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences

2013-06-20 Thread Volker Braun
On Wednesday, June 19, 2013 11:20:39 PM UTC-7, Nathann Cohen wrote: > > sage: from sage.combinat.combinatorial_map import combinatorial_map > sage: class C: > : @combinatorial_map > : def a(self,x): > : return x+1 > Thats not a benchmark, thats masturba

Re: [sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences

2013-06-20 Thread Nathann Cohen
> Thats not a benchmark, thats masturbating over the call overhead. Volker, could you please read aloud the sentence which followed immediately this example of code ? "That's a 3x in a non-existing case, which make it almost negligible for any application, and that is not even my point. WHY shoul

Re: [sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences

2013-06-20 Thread Volker Braun
On Thursday, June 20, 2013 7:37:07 AM UTC-7, Stefan wrote: > Nathann's complaint about the out-of-control growth of methods of the > Graph object is a very valid issue I think we talked about that a few months ago. One should first evaluate whether all / most methods really make sense for all

[sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences

2013-06-20 Thread Volker Braun
On Thursday, June 20, 2013 12:17:48 AM UTC-7, Simon King wrote: > And this should really not be done on the level of the method being > registered. There should be a database of "useful combinatorial maps", and > the decorator should do nothing more than adding a method to this > database. >

[sage-devel] Sage 5.10 released

2013-06-20 Thread Jeroen Demeyer
Sage 5.10 was released on 17 June 2013. It is available in source and binary form from: * http://www.sagemath.org/download.html Sage (http://www.sagemath.org/) is developed by volunteers and combines over 90 open source packages. For instructions about installing Sage, see * http://www.sage

Re: [sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences

2013-06-20 Thread Stefan
> > First of all, before ranting about speed someone should measure the slow > > down. If I remember correctly, we already did it once with Christian and > the > > slow down was less than 10% which is in my opinion perfectly acceptable. > If an > > error was made, it is that we didn't keep any

Re: [sage-devel] Re: Sqrt simplification

2013-06-20 Thread Eric Gourgoulhon
Thanks for your explanation. So it is clear that radcan ignore assumptions. As already mentioned by kcrisman, radcan does not take into account the option variable radexpand, which, if set to 'true' (and domain to 'real'), would do the job, as suggested in the documentation http://maxima.sourcef

[sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences

2013-06-20 Thread Dima Pasechnik
On 2013-06-20, Simon King wrote: > Hi! > > On 2013-06-20, Nathann Cohen wrote: >> And I can also add to this comment that you can actually implement this >> feature using decorators at no cost, because you can do this without >> changing the function at all. If you want a decorator that does that

[sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences

2013-06-20 Thread Dima Pasechnik
On 2013-06-19, Nathann Cohen wrote: > --20cf301ee7a5191d5204df850b33 > Content-Type: text/plain; charset=ISO-8859-1 > > Hello everybody ! > > I just noticed in today's release the presence of two tickets that I had > missed while they were being reviewed, and I really regret it. > > Those

[sage-devel] Re: find_stat in Sage, the combinatorial_map decorator and its consequences

2013-06-20 Thread Simon King
Hi! On 2013-06-20, Nathann Cohen wrote: > And I can also add to this comment that you can actually implement this > feature using decorators at no cost, because you can do this without > changing the function at all. If you want a decorator that does that > > @find_stat_properties(surjective = Tr