Oh, I forgot to mention that there is a big plus for running in the same process as the editor. In Emacs the communication with the inferior process comes at a price. I had to serialize the data (through json and through a file) that I pass between elisp and python. Running in the same process as the editor means the Leo script has direct access to my data, which makes exploring data even more natural.
On Tue, Oct 2, 2012 at 11:18 AM, Edward K. Ream <edream...@gmail.com> wrote: >> I have large data sets that take time to load and process into Python >> memory. Somehow it feels hazardous to load them into the same process as my >> editor :-) > > Your intuition is probably faulty. Loading large data into Leo should be > safe. > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
