On Tue, 3 Aug 2010 09:26:32 -0500
Kent Tenney <[email protected]> wrote:
> This also led to a discussion of how Leo should treat non-class /
> non-method declarations
> mixed in with classes and methods. Currently Leo places them in with
> the following class/method.
>
> I don't think that's a good solution.
Spent 3-4 minutes just yesterday looking for a declaration buried in an
irrelevant node.
Module level code:
TableEntry = namedtuple('TableEntry', 'tablename id parentref childlist
keyfields lookups')
# ChainEntry = namedtuple('ChainEntry', 'table id')
def recordHash(record):
"""make a hash of a a record"""
return hash(record) # try internal for now
was all pushed in to the def node.
Whitespace wise that might be reasonable, but then that's not the whitespace as
I typed it, but as it ended up after Leo messed with it :-}
Cheers -Terry
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
