On 16/04/2006, at 11:40 PM, Norman Rasmussen wrote: > On 3/14/06, Norman Rasmussen <[EMAIL PROTECTED]> wrote: >> I'm pretty sure that this error is 'left over' from the startup, so >> there's no real stack trace at all. I think a few sys.exc_clear()'s >> might be in order. I've found that python doesn't keep track of where >> the exception applies to so well. I've added the exc_clear's in >> main.py, and we'll see how it goes. > > Here's the patch if you're interested:
Ok. I finally figured out exactly what's causing this! :) If you're interested... >>> help(twisted.internet.defer.Deferred.errback) <snip> If the argument that's passed to me is not a failure.Failure instance, it will be embedded in one. If no argument is passed, a failure.Failure instance will be created based on the current traceback stack. <snip> So basically, we have to have an argument whenever we call errback() on a Deferred. Easy eh? Thanks for your patience Norman. Daniel, PyAIM-t has a few carried over from PyMSNt, look in disco.py and session.py You might have others too. Hurrah! :) --- James
