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

2016-01-03 Thread William Stein
On Sun, Jan 3, 2016 at 1:49 PM, Emmanuel Charpentier wrote: > > > Le dimanche 3 janvier 2016 21:23:56 UTC+1, Volker Braun a écrit : >> >> On Sunday, January 3, 2016 at 5:36:30 PM UTC+1, Emmanuel Charpentier >> wrote: >>> >>> [ BTW : that's not really a bug, but rather a design conflict : the >>> o

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

2016-01-03 Thread Volker Braun
We can't (and shouldn't) change how Jupyter extracts arguments. Its either line magic %magic one line of argument or cell magic %%magic argument more argument Note that the "coding problems" are not that small : ensuring that r(...), > %r, %R and %%R "speak" to the same instance of R does not

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

2016-01-03 Thread Emmanuel Charpentier
Le dimanche 3 janvier 2016 21:23:56 UTC+1, Volker Braun a écrit : > > On Sunday, January 3, 2016 at 5:36:30 PM UTC+1, Emmanuel Charpentier wrote: >> >> [ BTW : that's not really a bug, but rather a design conflict : the >> original %mode functions were designed to switch (for an indefinite scope

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

2016-01-03 Thread Volker Braun
On Sunday, January 3, 2016 at 5:36:30 PM UTC+1, Emmanuel Charpentier wrote: > > [ BTW : that's not really a bug, but rather a design conflict : the > original %mode functions were designed to switch (for an indefinite scope) > the behaviour of the REPL.This was transposed in the Sage notebook as

[sage-devel] Re: OSX binaries (including El Capitan)

2016-01-03 Thread Harald Schilly
On Sat, Jan 2, 2016 at 8:19 PM, Volker Braun wrote: > We should probably always word things as "OSX 10.4 and higher" and not "OSX > 10.4 - OSX 10.$CURRENT'" > > Harald, can you change the text on that page? yes, I'm currently fixing this. -- h -- You received this message because you are subsc

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

2016-01-03 Thread Jeroen Demeyer
On 2016-01-03 17:36, Emmanuel Charpentier wrote: how to define the function in the global namespace as in the command line or Sage notebook... The relevant compile_and_load() function returns a module (from which one can of course import *, which would mimic the current Sage notebook behavior) ;

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

2016-01-03 Thread Volker Braun
On Sunday, January 3, 2016 at 6:19:53 PM UTC+1, William wrote: > > In case you are curious, in SageMathCloud worksheets a line mode is > > %foo > > and a cell mode is > > %foo(optional, arguments) > Thats almost the same except for the second percent sign in the cell magic %%foo FWIW th

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

2016-01-03 Thread William Stein
On Sun, Jan 3, 2016 at 8:36 AM, Emmanuel Charpentier wrote: > Dear Volker, > > Le dimanche 3 janvier 2016 16:33:36 UTC+1, Volker Braun a écrit : >> >> On Sunday, January 3, 2016 at 2:41:51 PM UTC+1, Emmanuel Charpentier >> wrote: >>> >>> "other language" cells : %maxima and %r (possibly other inte

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

2016-01-03 Thread Emmanuel Charpentier
Dear Volker, Le dimanche 3 janvier 2016 16:33:36 UTC+1, Volker Braun a écrit : > > On Sunday, January 3, 2016 at 2:41:51 PM UTC+1, Emmanuel Charpentier wrote: >> >> >>- "other language" cells : %maxima and %r (possibly other >>interpreters such as %octave) do not work as expected. Both %m

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

2016-01-03 Thread Volker Braun
On Sunday, January 3, 2016 at 2:41:51 PM UTC+1, Emmanuel Charpentier wrote: > > >- "other language" cells : %maxima and %r (possibly other interpreters >such as %octave) do not work as expected. Both %maxima and %r open new >instances of their respective interpreters and enter an REPL

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

2016-01-03 Thread Emmanuel Charpentier
Omitted from the previous ran^Kpost (and thus is probably still quite incomplete...) : - (Very ?) serious : no %cython cells, and no "obvious" shortcut to get them. The "semi-obvious" replacement (%%writefile + load()) is not *that* obvious to realize "cleanly" (no left-over files, et

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

2016-01-03 Thread Jeroen Demeyer
On 2016-01-03 14:41, Emmanuel Charpentier wrote: * Interacts : In a Python worksheet, ipywidgets offers a nice interactive framework, ... which turns out no be non obvious to use from a Sage worksheet. A replacement and/or a compatibility layer are needed. (Even if we offer a replac

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

2016-01-03 Thread Emmanuel Charpentier
Le dimanche 3 janvier 2016 03:52:35 UTC+1, Jonathan a écrit : > > This looks like you are on the correct track. I would just urge you to > indicate what features of Sagenb are not available yet. > A few things pop to my mind. I already signaled some f them (some might say I ranted about them)

Re: [sage-devel] Finite State Machine Improvements

2016-01-03 Thread Clemens Heuberger
Hi, Am 2016-01-03 um 07:00 schrieb Marco Cognetta: > Hi, > > I would like to implement some of the closure operations that are missing from > the finite state machine code. Since there are several that are not > implemented > (intersection, difference, reversal, homomorphism, and inverse homom

Re: [sage-devel] Finite State Machine Improvements

2016-01-03 Thread David Roe
On Sat, Jan 2, 2016 at 10:00 PM, Marco Cognetta wrote: > Hi, > > I would like to implement some of the closure operations that are missing > from the finite state machine code. Since there are several that are not > implemented (intersection, difference, reversal, homomorphism, and inverse > homo

[sage-devel] Finite State Machine Improvements

2016-01-03 Thread Marco Cognetta
Hi, I would like to implement some of the closure operations that are missing from the finite state machine code. Since there are several that are not implemented (intersection, difference, reversal, homomorphism, and inverse homomorphism; with only intersection being currently included in the

Re: [sage-devel] New developer willing to contribute [help]

2016-01-03 Thread Jori Mäntysalo
On Sat, 2 Jan 2016, Karan Desai wrote: I will take a few days, probably a week to try to understand the framework as a whole, I doubt if few days are enought for this. At least for me few years is not enought. :=) and pick up a small part of it and go deep within to see how things work spe