W liście chris van z dnia środa, 18 lutego 2009: > Thanks for the response Mike, > > I used print only as an example, my actual application code doesn't use > print at all. I replaced the print statement with a call to log.debug such > that the code now looks like this: ... > for i in range(10) > log.debug(i) > ...
I'm 99.9999% sure it has nothing to do with the for loop. It should also happen if you do i=0 log.debug(i) The trace is confusing nonetheless (and either invalid or truncated). -- Paweł Stradomski --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
