This has indeed happened to us in the past. If I recall, someone told us
about it a while back and we just assumed it was one of those things you had
to deal with.  When it does happen it seems to be a random occurrence.
Perhaps it is (or was) a Wing related issue.

Larry Long

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of johnf
Sent: Tuesday, October 23, 2007 12:24 PM
To: Dabo developers' list
Subject: Re: [dabo-dev] Wacky Update

On Tuesday 23 October 2007 09:15, Uwe Grauer wrote:
> johnf wrote:
> > 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.
>
> Do you have a testcase for this "comment bug"?
> I just can't believe it.
>
> Uwe
We did at one point!  Like I said it was repeatable.  I believe Larry can
confirm.  Also any test case we could provide would be a little to large and
require far to many dependencies to be a simple test case.  I like to think
I'm a practical programmer meaning that if removing a comment allows the 
program to run then I remove the comment.   If there was some other cause 
like formatting or some other issue I really did not see it.  So for now I
never use a comment immediately after def or class - only triple quotes.

-- 
John Fabiani


[excessive quoting removed by server]

_______________________________________________
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/!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAafA2fnYuPUOMNFpIYnBEQcKAAAAQAAAAd98Ye2v/[EMAIL
 PROTECTED]

Reply via email to