Getting ipython-exec working

Hi, While I'm able to see IPython variables in Leo and Leo variables in IPython and can't seem to get Leo nodes to execute in IPython. When I hit ctrl-shift-i with a Leo node selected, nothing seems to happen. Is this what's supposed to happen? ...in Leo: ctrl-shift-i on node with body: b =100

Re: Configuration Screipt Pattern

Thanks Jacob and Terry, This is really helpfull. I didn't know about c.config.getxxx, that seems like a good way to start. Rafi -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it,

Re: Configuration Screipt Pattern

On Mon, 21 Dec 2015 12:47:54 -0500 Jacob Peck wrote: > The convention tends to be using @settings trees and the appropriate > c.config.getX() methods, but obviously that only works for scripts > run within Leo. If you're writing a script for use both within and > outside

Re: Jupyter vs IPython

OK, when I first got this I thought the issue stemmed from the ShimWarning, thus the name of the post. While the ShimWarning stands, the real issue is finding the kernel connection information. I'm using Anaconda and the kernel connection files, e.g., kernel-9.json are being written to

Configuration Screipt Pattern

What's the pattern for creating Python configuration files in Leo? Should Leo create a file which the script then reads or should the script try to key off of Leo nodes directly? I'm new to Leo, so I'm sorry if I'm asking the obvious. Thanks in advance, Rafi -- You received this message

Re: Configuration Screipt Pattern

On Mon, 21 Dec 2015 07:17:53 -0800 (PST) Rafi Bin-Nun wrote: > What's the pattern for creating Python configuration files in Leo? > Should Leo create a file which the script then reads or should the > script try to key off of Leo nodes directly? You might need to

Re: Configuration Screipt Pattern

Thanks Terry, Let me re-phrase the question in those terms... When running Python scripts from Leo, should Leo build a configparser config file and have the python script read it in with configparser.read(), or should the Python script pull the configuration information directly from Leo

Re: Configuration Screipt Pattern

The convention tends to be using @settings trees and the appropriate c.config.getX() methods, but obviously that only works for scripts run within Leo. If you're writing a script for use both within and outside of Leo, you might want to go the other way. My personal Leo scripts tend to hold