On Tuesday 23 October 2007 08:14, Nate Lowrie wrote:
> On 10/22/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > Is it perhaps the comments? I thought that we were not supposed to put
> > comments immediately after class or def segments.
>
> No, the comments are fine...
>
> Ed, I don't see the error.  Does it fire when you remove the manual
> update binding?  Does it fire when you remove the KeyChar event?  It
> should work, especially if you are getting the "FORM UP" and "PNL UP"
> messages.
>
> Nate L.
That is what I thought until we started seeing strange behavior from python 
due to comments.  Larry is not talking about triple quotes but '#' comments.  
For example in the middle of a large app we would have something like.

def something(self):
# added some comment - normally it would say 'pass'
        here is the code

We were creating dummy def's (place holders) with a 'pass' then later would 
just comment it out.   If fact at some point were able to repeat the issue.  
All we did was remove the # comment and all started working.  Larry and I are 
running python 2.5.1.

-- 
John Fabiani


_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/dabo-dev/[EMAIL PROTECTED]

Reply via email to