Re: [sage-devel] message to patchbot breeders

On Wednesday, 15 April 2015 21:55:34 UTC+1, Frédéric Chapoton wrote: > > Hello, > > As I have said before, I have no machine other than my laptop, so I only > test the patchbot on my own sage installation on that laptop. > Should we find a machine for you to run patchbot, if your university is

Re: [sage-devel] Re: Race condition when closing tickets

Out of my previous list, there were some false positives (I somehow mishandled invalid tickets). Five incompletely merged tickets remained. Am 2015-04-16 um 07:20 schrieb Clemens Heuberger: > ticket commit changed > 15017 872e2bc0225b6929ed8cc052a63850c892abe723

[sage-devel] Broken options of show() in Sage 6.6

Hi, In Sage 6.6, it seems that the options passed to show() for displaying a 3D object are not taken into account: sage: show(sphere(), figsize=10, frame=False, aspect_ratio=(1,1,0.5)) gives the same output as a mere show(sphere()). This issue occurs both with the default viewer (Jmol) as wit

[sage-devel] installation of optional spkg's on binary Sage releases

It seems to me that binary distributions are not guaranteed to be able to build some optional packages. There were numerous reports on sage-support, and here is another example: http://trac.sagemath.org/ticket/18198 However, reading http://sagemath.org/doc/installation/quick-guide.html gives you

Re: [sage-devel] installation of optional spkg's on binary Sage releases

On Thu, Apr 16, 2015 at 9:49 AM, Dima Pasechnik wrote: > It seems to me that binary distributions are not guaranteed to be able to > build some optional packages. Side question -- Is anything guaranteed to build all optional packages? What's the current status of testing them? I keep raising t

Re: [sage-devel] Re: Race condition when closing tickets

> > On Thursday, April 16, 2015 at 7:58:32 AM UTC+2, Jeroen Demeyer wrote: >> >> On 2015-04-16 01:33, Nils Bruin wrote: >> > The whole meaning of "positive review" goes out of >> > the window if one still changes the branch on the ticket. >> I disagree. It can easily happen that a problem is

Re: [sage-devel] installation of optional spkg's on binary Sage releases

On Thursday, 16 April 2015 18:12:16 UTC+1, William wrote: > > On Thu, Apr 16, 2015 at 9:49 AM, Dima Pasechnik > wrote: > > It seems to me that binary distributions are not guaranteed to be able > to > > build some optional packages. > > Side question -- Is anything guaranteed to build all op

Re: [sage-devel] Re: Race condition when closing tickets

Am 2015-04-16 um 19:28 schrieb kcrisman: > That said, now that I see part of the problem is not just people changing > tickets, but changing *branches* and *keeping* positive review (or something > analogous to this), I agree that is a different situation. So, here's my > possibly buggy suggestion

[sage-devel] Please review trac#18229.

Small change ticket : upgrade R to 3.1.3. That's trac#18229 . HTH, -- Emmanuel Charpentier -- 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: Broken options of show() in Sage 6.6

Hell, This problem is very common with functions that take **args as input. It usually isn't hard to fix: you just have to make sure that a function taking **args as input will *ALWAYS* call another function with **args as argument. At the end of the call there should be some functi

Re: [sage-devel] installation of optional spkg's on binary Sage releases

> > Side question -- Is anything guaranteed to build all optional > packages? What's the current status of testing them? I keep raising > this issue... > If you ever get tired of raising the issue, maybe you could try doing something about it. Nathann -- You received this message becau

[sage-devel] Bad display of tuples in Sage 6.6 notebooks

Hi, In Sage 6.6 notebooks (either Sage notebook or IPython notebook), tuples are displayed without parenthesis nor comma (!) when the LaTeX typeset mode is turned on (i.e. with 'typeset' box clicked in the Sage notebook or with %display latex in the IPython notebook): input: (1,2) output: *12*