On Thu, Apr 10, 2008 at 11:42 AM, Ville M. Vainio [EMAIL PROTECTED]
wrote:
You'll probably want to check out the new ipy_autoreload extension
Thanks for this tip.
Edward
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Hi,
I've started using Leo about 2 months ago. I intended to use it as a
single point of entry for a Python toolkit I am writing from scratch,
where the code is closely coupled with documentation and tests.
My biggest stumbling block is that I find it hard to break out of a
file-based way of
Any tips for a Leo newbie on how to start a project from scratch?
Here's a quote from the docs: @thin - Use this unless you have a good
reason not to. It is the 'state-of-the-art' in derived files.
I had a bad experience when trying to import derived files into leo as
@file. After a couple of
Hi,
Yes, I remember now - I did use @thin for all derived files. I haven't
actively used Leo for the past few weeks, so the terminology is
slipping...
My problem has to do with starting with a blank myproject.leo. I don't
have a clear idea of how to proceed. I initially thought I'll do a top-
On Thu, Apr 10, 2008 at 7:43 AM, Ludwig Schwardt [EMAIL PROTECTED]
wrote:
When I tried to go deeper, I found it really hard to decide which
files I needed where in the Leo hierarchy. And what if the code in one
node needed code in another node? Do I clone it into the required
node, or do I
On Thu, Apr 10, 2008 at 08:44:39AM -0500, Edward K. Ream wrote:
For programming projects, I organize my master .leo file in two ways: by
topic (Notes, Projects, To Do) and by file. I use @thin files like
leoNotes.txt, leoProjects.txt, leoToDo.txt and leoToDoLater.txt to keep the
actual .leo
On Thu, Apr 10, 2008 at 7:16 PM, Kayvan A. Sylvan [EMAIL PROTECTED] wrote:
with my python code (import a file, play with its classes, test out my
ideas), then update the code in Leo and back in ILeo, just reload the
module
and continue playing, ad infinitum. I get all the power of
