Re: jupyter files

2017-08-30 Thread Edward K. Ream
he simplest solution and works fine for the latex > files. > > It won't work out of the box for jupyter files, since these contain all > kind of stuff which should not go into the normal python node bodies, > but still need to be written back if we want to round-trip jupyter files. > If

Re: jupyter files

2017-08-29 Thread Josef
not using Leo. >> > > ​Why is this a problem? Just read the file into @auto the first time, > then change it to @clean.​ > Doh! Of course that is the simplest solution and works fine for the latex files. It won't work out of the box for jupyter files, since these c

Re: jupyter files

2017-08-26 Thread Offray Vladimir Luna Cárdenas
On 26/08/17 12:43, Edward K. Ream wrote: > On Sat, Aug 26, 2017 at 10:11 AM, Offray Vladimir Luna Cárdenas > > wrote: > > > Usually the collaboration between Leo and other languages has been > by being able to read/parse what these languages

Re: jupyter files

2017-08-26 Thread Edward K. Ream
On Sat, Aug 26, 2017 at 10:11 AM, Offray Vladimir Luna Cárdenas < off...@riseup.net> wrote: Usually the collaboration between Leo and other languages has been by being > able to read/parse what these languages store (*ipynb, *html, *js, etc) and > convert them into a Leo tree to extend,

Re: jupyter files

2017-08-26 Thread Edward K. Ream
ile, while I am > skeptical about them using Leo - sadly. > ​I suggest not worrying about your co-workers just yet ;-) Let's focus on converting to and from Jupyter files in a way that works for you. >> ​Interesting idea. The present .ipynb importer is just that: only an >> import

Re: jupyter files

2017-08-26 Thread Offray Vladimir Luna Cárdenas
Hi, I think that exploratory computing (as Fernando Perez, co-lead dev of Jupyter) would benefit largely from Leo capabilities and outlining, as argued here, in this list, and on the web [1], because of the emergent self-organizing nature of outlines and such kind of computation, and one of the

Re: jupyter files

2017-08-26 Thread Josef
On Tuesday, 22 August 2017 20:48:56 UTC+2, Edward K. Ream wrote: > > On Tue, Aug 22, 2017 at 7:32 AM, Josef > wrote: > >> For me it is all about usability. >> > > ​Yes. People like you who actually use Jupyter have insights that I don't > have. I welcome all your

Re: jupyter files

2017-08-22 Thread Edward K. Ream
On Tue, Aug 22, 2017 at 7:32 AM, Josef wrote: > For me it is all about usability. > ​Yes. People like you who actually use Jupyter have insights that I don't have. I welcome all your suggestions. ​> ​ I want to be able to write code, clone bits and pieces here and there,

Re: jupyter files

2017-08-22 Thread Josef
For me it is all about usability. I found working with Leo I can relatively easy move around bits and pieces of code and experiment with different schenarios, and still keep the overview if the code gets large. This is a clear advantage over Jupyter, where the code is rather monolithic, or

Re: jupyter files

2017-08-21 Thread Edward K. Ream
On Mon, Aug 21, 2017 at 7:17 AM, Josef wrote: > Leo's @auto reads in .ipynb files, and there are now @pyplot commands, but > I am lost at how to use these. > ​At present these are two separate features. #477 hints at

jupyter files

2017-08-21 Thread Josef
Leo's @auto reads in .ipynb files, and there are now @pyplot commands, but I am lost at how to use these. Ok, the @auto *.ipynb node contains the python source and more, but unless I delete all the # subnodes and add an @others, I can't execute the script, and I don't see what @pyplot does. I