I'd like to spend some time in making sagecell working, and even of course contribute to this wonderful project if I am able to.
But I have to be sure that I can reach the following goals:
1. make sagecell working in my development environment ArchLinux 2. playing with sagecell with "sage" and "matlab" interpreters (like I did with previous sage notebook) 3. saving a variable ("out") in a database (it would be great to save it as a ".mat" and as "sage" variable) 4. deploy sage+matlab+sagecell on Debian squeeze
My requirement is to support matlab by default (unfortunately...) so if you think it is feasible I am going to proceed, otherwise I have to find an hack to let the actual sage notebook working as a backend for my application instead of sagecell.
At this time every weird hack you can think about to reach the goals are going to be accepted by me :)
> I'd like to spend some time in making sagecell working, and even of course > contribute to this wonderful project if I am able to.
> But I have to be sure that I can reach the following goals:
> 1. make sagecell working in my development environment ArchLinux
> 2. playing with sagecell with "sage" and "matlab" interpreters (like I did > with previous sage notebook)
> 3. saving a variable ("out") in a database (it would be great to save it > as a ".mat" and as "sage" variable)
> 4. deploy sage+matlab+sagecell on Debian squeeze
> My requirement is to support matlab by default (unfortunately...) so if > you think it is feasible
> I am going to proceed, otherwise I have to find an hack to let > the actual sage notebook working as a backend for my application
> instead of sagecell.
> At this time every weird hack you can think about to reach the goals are > going to be accepted by me :)
Il giorno venerd́ 3 agosto 2012 11:15:41 UTC+2, fero ha scritto:
> The problem that I have now in sagecell is that:
> * matlab("3**2") --> is not able to spawn the matlab interpreter
this one has been "solved" ! I found that matlab was not spawn because /usr/local/bin
was not in the PATH when I execute "sage-native-execute"
that is called also by sage_device
pexepect_env variable
local/lib/python2.7/site-packages/sage/interfaces/expect.py
line 464
at the moment I linked the executable in /usr/bin I have no more time to investigate on this.
Pay attention that if I do
import os; os.getenv("PATH") in sagecell, I see /usr/local/bin directory among results.
>> I'd like to spend some time in making sagecell working, and even of >> course contribute to this wonderful project if I am able to.
>> But I have to be sure that I can reach the following goals:
>> 1. make sagecell working in my development environment ArchLinux
>> 2. playing with sagecell with "sage" and "matlab" interpreters (like I >> did with previous sage notebook)
>> 3. saving a variable ("out") in a database (it would be great to save it >> as a ".mat" and as "sage" variable)
>> 4. deploy sage+matlab+sagecell on Debian squeeze
>> My requirement is to support matlab by default (unfortunately...) so if >> you think it is feasible
>> I am going to proceed, otherwise I have to find an hack to let >> the actual sage notebook working as a backend for my application
>> instead of sagecell.
>> At this time every weird hack you can think about to reach the goals are >> going to be accepted by me :)
> I'd like to spend some time in making sagecell working, and even of
> course contribute to this wonderful project if I am able to.
> But I have to be sure that I can reach the following goals:
> 1. make sagecell working in my development environment ArchLinux
> 2. playing with sagecell with "sage" and "matlab" interpreters (like I
> did with previous sage notebook)
> 3. saving a variable ("out") in a database (it would be great to save it
> as a ".mat" and as "sage" variable)
> 4. deploy sage+matlab+sagecell on Debian squeeze
> My requirement is to support matlab by default (unfortunately...) so if
> you think it is feasible
> I am going to proceed, otherwise I have to find an hack to let
> the actual sage notebook working as a backend for my application
> instead of sagecell.
> At this time every weird hack you can think about to reach the goals are
> going to be accepted by me :)
Just FYI, the code (and docs) in the root sagecell directory is version 1 of the code, and is not under development anymore. We are instead doing active development in the codebase in contrib/ipython-testing/. Like I mentioned before, the instructions are at
Apparently they didn't work for 5.2, so thanks for looking at updating them. I just downloaded and compiled 5.2 last night so that I can look at your updated patch sometime tonight or tomorrow, hopefully.
To start, just do "sage web_server.py" in the contrib/ipython-testing directory.
My installation of sagecell version 1 works quite well for my needs now.
Only thing that I lack is to let the user switch from sage/matlab interpreter.
I will stay on sagecell version 1 now, or taking again the sage notebook,
If I don't succeed in using sagecell interpreter switching.
Il giorno venerd́ 3 agosto 2012 17:45:04 UTC+2, jason ha scritto:
> On 8/3/12 12:50 AM, fero wrote: > > I am still fixing something to reach the end of the installation > > procedure described at > > https://github.com/sagemath/sagecell
> > I'd like to spend some time in making sagecell working, and even of > > course contribute to this wonderful project if I am able to.
> > But I have to be sure that I can reach the following goals:
> > 1. make sagecell working in my development environment ArchLinux > > 2. playing with sagecell with "sage" and "matlab" interpreters (like I > > did with previous sage notebook) > > 3. saving a variable ("out") in a database (it would be great to save it > > as a ".mat" and as "sage" variable) > > 4. deploy sage+matlab+sagecell on Debian squeeze
> > My requirement is to support matlab by default (unfortunately...) so if > > you think it is feasible > > I am going to proceed, otherwise I have to find an hack to let > > the actual sage notebook working as a backend for my application > > instead of sagecell.
> > At this time every weird hack you can think about to reach the goals are > > going to be accepted by me :)
> Just FYI, the code (and docs) in the root sagecell directory is version > 1 of the code, and is not under development anymore. We are instead > doing active development in the codebase in contrib/ipython-testing/. > Like I mentioned before, the instructions are at
> Apparently they didn't work for 5.2, so thanks for looking at updating > them. I just downloaded and compiled 5.2 last night so that I can look > at your updated patch sometime tonight or tomorrow, hopefully.
> To start, just do "sage web_server.py" in the contrib/ipython-testing > directory.
