[Python-Dev] The impact of '@' on Leo

[Fred L. Drake, Jr.]

On Thursday 05 August 2004 10:41 pm, Greg Ewing wrote:
 > But maybe it would be a good idea to explicitly reserve some
 > character (perhaps only at the beginning of a line).

Bob Ippolito responded:
 > You mean like # ?

Yeah, like that.  ;-)  That's always accepted as the first non-blank character 
on a non-continuation line, and the only thing Python ever cares about after 
that are the encoding turd and a newline.  Anything after the newline is, 
well, another line.

I've really only managed to look at Leo much once, and Edward was sitting next 
to me at the time.  Leo doesn't store Python code in a Leo document as any 
sort of embedded object that's labelled as Python code as far as I can tell 
(though it may in it's data model); it just more text, and can have 
@directives like any other text.  I think this is inherently a risky approach 
to the data; there needs to be at least a way to say that some portion of the 
data is some other text format embedded into the Leo document.

I'm sure Edward can find a way to make things work for Leo users, but I hope 
the .leo files have some sort of format version indicator to make upgrading 
relatively easy for Leo users.


  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at acm.org>