[sage-devel] Re: sage called from texmacs will not start

I needed the svn version because we are using the Greek language that was being developed at the time. However, some students used the stable version and still had problems with sage. My apologies for the very late response; I was expecting to get notified by the e-mail of any answers. Quite b

[sage-devel] Re: sage called from texmacs will not start

Yes, I do have which. My apologies for the very late response; I was expecting to get notified by the e-mail of any answers. -- 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 a

[sage-devel] Re: Build failure on Debian testing

Yep. That was it. The bug is now closed. I updated and then successfully compiled sage. On Friday, December 18, 2015 at 9:53:22 AM UTC-5, Emmanuel Charpentier wrote: > > Le jeudi 17 décembre 2015 22:33:45 UTC+1, Volker Braun a écrit : >> >> This should be https://bugs.debian.org/cgi-bin/bugrepor

Re: [sage-devel] About SetPartition.to_permutation

Yo, Please excuse my sarcastic responses before. I find it hard to deal with > being told off when trying to contribute. > Don't take it bad, it is the same for all of us here. Wanna know how many tickets I opened just to give them up two days later, because people did not like them

Re: [sage-devel] dumping and loading 2D and 3D graphic objects

Hello William, thanks a lot for your rapid reply. Ok, for the moment I will restrict the plot parallelization to 2D graphics only. Later, I will try to follow your suggestion and reduce the parallized object to something pickle-able. Best regards, Marco Le vendredi 18 décembre 2015 16:08:52

[sage-devel] Re: Jupyter notebook by default?

IMHO the Jupyter/IPython notebook is a clear winner, no real contest. Nobody prevents you form using SageNB for existing worksheets or the live documentation; But if you start a new worksheet today then you really should be using Jupyter. On Friday, December 18, 2015 at 11:35:53 AM UTC+1, Jero

Re: [sage-devel] dumping and loading 2D and 3D graphic objects

On Fri, Dec 18, 2015 at 6:50 AM, mancio wrote: > Hello, > > I am experimenting some problem concerning the pickling of 3D graphic > objects. > > Here the exemple: > > 2D) > c = circle((1,1), 1) > show(loads(dumps(c))) > > And I get the 2D plot of the circle > > 3D) > c = circle((1,1,1), 1) > d = l

[sage-devel] dumping and loading 2D and 3D graphic objects

Hello, I am experimenting some problem concerning the pickling of 3D graphic objects. Here the exemple: 2D) c = circle((1,1), 1) show(loads(dumps(c))) And I get the 2D plot of the circle 3D) c = circle((1,1,1), 1) d = loads(dumps(c)) I get the warining: ./local/lib/python2.7/site-pac

Re: [sage-devel] Re: Jupyter notebook by default?

On Fri, Dec 18, 2015 at 6:47 AM, Emmanuel Charpentier wrote: > A few addenda : > > Pros : > * The python debugger works in the IPython notebook. Damn useful ! > * Some extensions developed for Python worksheets run in Sage worksheets. > > Cons : > * (Currently) no standard way to create a cell

[sage-devel] Re: Build failure on Debian testing

Le jeudi 17 décembre 2015 22:33:45 UTC+1, Volker Braun a écrit : > > This should be https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808205 > This *is* it. I've been bitten by this one. I just installed the binutils version from unstable (which is now in testing, by the way). The Debian develop

[sage-devel] Re: Jupyter notebook by default?

A few addenda : Pros : * The python debugger works in the IPython notebook. Damn useful ! * Some extensions developed for Python worksheets run in Sage worksheets. Cons : * (Currently) no standard way to create a cell in another language, as allowed by the Sage notebook's magics such as %maxi

Re: [sage-devel] Re: Build failure on Debian testing

Le vendredi 18 décembre 2015 01:19:17 UTC+1, Dima Pasechnik a écrit : > > > yeah, your compiler is too new... (I don't think we got Sage to build with > gcc 5; > Yes we got: Sage 6.10.rc2 compiles like a charm with gcc 5.2.1 under Ubuntu 15.10. Best wishes, Eric. -- You received this mes

[sage-devel] Jupyter notebook by default?

Should the Jupyter notebook be the default notebook for the next Sage 7.0 release? I don't really have an opinion on the matter. Pros: * Nice tracebacks! * The Jupyter notebook is a mature well-maintained project, unlike SageNB. It is widely used in the "scientific Python" community. * Avail

[sage-devel] Re: Sage 6.10.rc2 binaries test

Hi, I've tested sage-6.10.rc2-Ubuntu_15.10-x86_64.tar on a Ubuntu 15.10 computer and got the following issue: ./sage -n jupyter results in the error message: Please wait while the Sage Notebook server starts... [I 11:01:15.391 NotebookApp] Using MathJax: nbextensions/mathjax/MathJax.js [W 11:01:

Re: [sage-devel] About SetPartition.to_permutation

I tried to point out a possible improvement to the SetPartition code in http://trac.sagemath.org/ticket/19737, because I used this code. I also provided a patch. I was told that the original code is nonsensical. I disagree. In fact, from a recent experience with sage now disallowing empty ro

Re: [sage-devel] Re: Sage-7.0 ?

Hi, On Fri, Dec 18, 2015 at 08:14:42AM +0100, Jeroen Demeyer wrote: > On 2015-12-18 07:05, Andrey Novoseltsev wrote: > >We also hope to upgrade pexpect and do some nice changes in SageNB, > >although 7.0 is probably a great version to consider switching default > >notebook to IPython/Jupiter. (But

Re: [sage-devel] About SetPartition.to_permutation

On Friday, 18 December 2015 09:23:55 UTC, Martin R wrote: > > > > Am Freitag, 18. Dezember 2015 09:39:57 UTC+1 schrieb Dima Pasechnik: >> >> >> >> On Friday, 18 December 2015 08:33:05 UTC, Martin R wrote: >>> >>> Actually, I propose to delete all code from sage, because it doesn't >>> work in al

Re: [sage-devel] About SetPartition.to_permutation

Am Freitag, 18. Dezember 2015 09:39:57 UTC+1 schrieb Dima Pasechnik: > > > > On Friday, 18 December 2015 08:33:05 UTC, Martin R wrote: >> >> Actually, I propose to delete all code from sage, because it doesn't work >> in all circumstances. >> >> It might be useful for some people (not all that m

Re: [sage-devel] Re: Sage-7.0 ?

On Friday, December 18, 2015 at 8:14:46 AM UTC+1, Jeroen Demeyer wrote: > > There are some things which don't work yet in Sage on Jupyter, for > example interacts. SageNB interacts don't work, but Jupyter interacts do. The syntax is slightly different but it would be easy enough to provide a co

[sage-devel] Re: Sage-7.0 ?

William Stein wrote: > +1 the version! Anticipating the next +1, Sage 11.0. -leif > On Thursday, December 17, 2015, Francois Bissey > > wrote: > > +1 > > On 18/12/2015, at 12:42, Volker Braun > wrote: > > > > Should we switch to 7.

Re: [sage-devel] About SetPartition.to_permutation

On Friday, 18 December 2015 08:33:05 UTC, Martin R wrote: > > Actually, I propose to delete all code from sage, because it doesn't work > in all circumstances. > > It might be useful for some people (not all that many), but we are > actually doing them a favour because we save them from using s

Re: [sage-devel] About SetPartition.to_permutation

Actually, I propose to delete all code from sage, because it doesn't work in all circumstances. It might be useful for some people (not all that many), but we are actually doing them a favour because we save them from using software in circumstances where it doesn't apply. Thus, by deleting sa

[sage-devel] Re: Error installing package gcc-4.9.2.p1

On Friday, 18 December 2015 06:01:25 UTC, B. Lachele Foley wrote: > > As a non-privileged user, I used: > > $ ./configure --prefix=/path/to/sage-6.9 # I'm not convinced that the > prefix does anything... > $ make -j4 > > $ uname -a > Linux frost 3.2.0-79-generic #115-Ubuntu SMP Thu Mar