[sage-devel] Re: Poll: Supplemental graphical visualizations

[X ] Yes, I want graphical user interfaces that make use of the graphical abilities -- 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...@googleg

[sage-devel] Re: Poll: Supplemental graphical visualizations

> > > [X] Yes, I want graphical user interfaces that make use of the graphical > abilities > > Sounds like good design. The command that turns it off can then put into ~/.sage/init.sage -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubs

Re: [sage-devel] Re: Error building Sage (gcc-4.9.2.p1)

I thought it was in. Anyway it worked for me but as Leif said there may be further problems. Probably not in gcc though. Francois On 05/05/15 14:33, leif wrote: François Bissey wrote: I am afraid you'll need to get 6.7.beta3 to get the needed fix to build gcc with xcode 6.3.1. That fix [1] i

[sage-devel] Re: Error building Sage (gcc-4.9.2.p1)

François Bissey wrote: > I am afraid you'll need to get 6.7.beta3 to get the needed fix > to build gcc with xcode 6.3.1. That fix [1] is not even in Sage 6.7.beta3. The following /should/^TM work though: export GCC_CONFIGURE="--with-build-config=bootstrap-debug" make No guarantees; you ma

[sage-devel] Re: Poll: Supplemental graphical visualizations

[X] Yes, I want graphical user interfaces that make use of the graphical abilities Am Dienstag, 5. Mai 2015 00:54:15 UTC+8 schrieb Volker Braun: > > Since the last poll about graphics was immediately derailed by unrelated > command line questions, let me try once more: Should selected objects >

Re: [sage-devel] Error building Sage (gcc-4.9.2.p1)

I am afraid you'll need to get 6.7.beta3 to get the needed fix to build gcc with xcode 6.3.1. Francois On 05/05/15 12:53, Tynan Kelly wrote: Hi, I'm not a developer (at least not an expert!) and I'm having trouble building Sage from source. I get an error saying the following package(s) may ha

[sage-devel] Error building Sage (gcc-4.9.2.p1)

Hi, I'm not a developer (at least not an expert!) and I'm having trouble building Sage from source. I get an error saying the following package(s) may have failed to build: package: gcc-4.9.2.p1 I'm running OS X 10.10.3 and Xcode 6.3.1. I have tried building twice today, first using Sage 6.6,

[sage-devel] Re: Poll: Supplemental graphical visualizations

On Monday, May 4, 2015 at 8:40:24 PM UTC+2, John H Palmieri wrote: > > Try "graphs.RandomGNP(30,.5).show()" to get an idea of how uninstructive a >> plot can be (compared to anything you might say on its, diameter, degree >> distribution, planarity, etc...) :-P >> > I think that enough objects wi

[sage-devel] Re: Poll: Supplemental graphical visualizations

On Monday, May 4, 2015 at 8:32:53 PM UTC+2, Nathann Cohen wrote: > Just to complete Volker's question: it is not only about graphs, but in > general about objects whose graphical representations "adds something" > (there is a Matrix.plot, but that's not the subject). > In fact, that is relevant

[sage-devel] Re: Poll: Supplemental graphical visualizations

[X] Yes, I want graphical user interfaces that make use of the graphical abilities On Monday, May 4, 2015 at 11:32:53 AM UTC-7, Nathann Cohen wrote: > > Helloo, > > >> and any other representation of a graph is rather uninstructive >>> >> Err... Well. Try "graphs.RandomGNP(30,.5).show()

[sage-devel] Re: Poll: Supplemental graphical visualizations

Helloo, > and any other representation of a graph is rather uninstructive >> > Err... Well. Try "graphs.RandomGNP(30,.5).show()" to get an idea of how uninstructive a plot can be (compared to anything you might say on its, diameter, degree distribution, planarity, etc...) :-P Just to

[sage-devel] Re: Poll: Supplemental graphical visualizations

On Monday, May 4, 2015 at 10:48:50 AM UTC-7, Volker Braun wrote: > > Just to clarify, we are talking about the following: > OK, I'm neutral on that (so delete my vote from the count). I wouldn't normally think that a graph comes with a representation in the plane so I'd be a little surprised t

[sage-devel] Re: Poll: Supplemental graphical visualizations

[X ] Yes, I want graphical user interfaces that make use of the graphical abilities -- 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...@googleg

[sage-devel] Re: Poll: Supplemental graphical visualizations

Just to clarify, we are talking about the following: -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group

[sage-devel] Re: Poll: Supplemental graphical visualizations

On Monday, May 4, 2015 at 9:54:15 AM UTC-7, Volker Braun wrote: > > Since the last poll about graphics was immediately derailed by unrelated > command line questions, let me try once more: Should selected objects > display graphical visualizations when it can be done unobtrusively? We all > agre

[sage-devel] Poll: Supplemental graphical visualizations

Since the last poll about graphics was immediately derailed by unrelated command line questions, let me try once more: Should selected objects display graphical visualizations when it can be done unobtrusively? We all agree that this would be disturbing on the commandline. Mathematica does prec

Re: [sage-devel] A __reduce__ function handling **kwargs

On Monday, May 4, 2015 at 5:18:35 AM UTC-7, Nathann Cohen wrote: > > Yo ! > > > I guess it would be simpler to use __setstate__() in your use case. > > What is the difference between setstate and a helper function ? O_o > You should probably view the initial creation (whether it's a class cons

Re: [sage-devel] A __reduce__ function handling **kwargs

On 2015-05-04 14:18, Nathann Cohen wrote: Yo ! I guess it would be simpler to use __setstate__() in your use case. What is the difference between setstate and a helper function ? Not much, only that __setstate__() is a cleaner design and that __getstate__() is easier to doctest than __redu

Re: [sage-devel] A __reduce__ function handling **kwargs

Yo ! > I guess it would be simpler to use __setstate__() in your use case. What is the difference between setstate and a helper function ? O_o Nathann -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop recei

Re: [sage-devel] A __reduce__ function handling **kwargs

On 2015-05-04 13:55, Nathann Cohen wrote: Something vaguely like that is possible using __getstate__ and __setstate__, see http://trac.sagemath.org/ticket/18109 Err.. Well, in my case the function I call is not the class' constructor. That doesn't matter. I ended up writing an unpickle funct

Re: [sage-devel] A __reduce__ function handling **kwargs

> Something vaguely like that is possible using __getstate__ and __setstate__, > see http://trac.sagemath.org/ticket/18109 Err.. Well, in my case the function I call is not the class' constructor. Because of ... reasons :-P I ended up writing an unpickle function, which is more or less forwarding

Re: [sage-devel] A __reduce__ function handling **kwargs

Something vaguely like that is possible using __getstate__ and __setstate__, see http://trac.sagemath.org/ticket/18109 -- 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

Re: [sage-devel] Re: sage 6.6 & pyopenssl

It didn't work, there is no deprecation period for removing bugs. On Monday, May 4, 2015 at 11:14:43 AM UTC+2, Clemens Heuberger wrote: > > On 2015-05-04 10:55, Volker Braun wrote: > > We intentionally deleted the pyopenssl spkg. If it can be found on a > mirror then > > that is only because i

Re: [sage-devel] Re: sage 6.6 & pyopenssl

On 2015-05-04 10:55, Volker Braun wrote: > We intentionally deleted the pyopenssl spkg. If it can be found on a mirror > then > that is only because it hasn't been updated. > > This is http://trac.sagemath.org/ticket/18261 I am not too happy that the instructions in the documentation of the _cur

[sage-devel] Re: build sage-6.6 R fail

The libgd issue is fixed in #18293 On Monday, May 4, 2015 at 8:43:49 AM UTC+2, William wrote: > > Hi, > > I'm trying to build Sage-6.6 on the latest Ubuntu 14.10 > (SageMathCloud). The first problem was with libgd, which another > patch somebody posted May 1 got past. Now there is some myste

[sage-devel] Re: sage 6.6 & pyopenssl

We intentionally deleted the pyopenssl spkg. If it can be found on a mirror then that is only because it hasn't been updated. This is http://trac.sagemath.org/ticket/18261 On Monday, May 4, 2015 at 4:04:03 AM UTC+2, leif wrote: > > Clemens Heuberger wrote: > > I tried to install pyopenssl in or

Re: [sage-devel] Re: build sage-6.6 R fail

On 2015-05-04 09:05, leif wrote: William Stein wrote: I'm trying to build Sage-6.6 on the latest Ubuntu 14.10 (SageMathCloud). The first problem was with libgd, which another patch somebody posted May 1 got past. Now there is some mysterious error/crash when building R which means nothing to

[sage-devel] Re: build sage-6.6 R fail

leif wrote: > William Stein wrote: >> I'm trying to build Sage-6.6 on the latest Ubuntu 14.10 >> (SageMathCloud). The first problem was with libgd, which another >> patch somebody posted May 1 got past. Now there is some mysterious >> error/crash when building R which means nothing to me. See a

[sage-devel] Re: build sage-6.6 R fail

William Stein wrote: > I'm trying to build Sage-6.6 on the latest Ubuntu 14.10 > (SageMathCloud). The first problem was with libgd, which another > patch somebody posted May 1 got past. Now there is some mysterious > error/crash when building R which means nothing to me. See attached > log. I'