!!! Holy crap, thanks Norman! That may explain one of the odd errors I was seeing reported.
Daniel On Apr 16, 2006, at 9:40 AM, 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: > > Index: src/main.py > =================================================================== > --- src/main.py (revision 137) > +++ src/main.py (working copy) > @@ -11,16 +11,20 @@ > try: > from twisted.internet import epollreactor as bestreactor > except: > + sys.exc_clear() > try: > from twisted.internet import kqreactor as bestreactor > except: > + sys.exc_clear() > try: > from twisted.internet import pollreactor as > bestreactor > except: > + sys.exc_clear() > try: > from twisted.internet import > selectreactor as bestreactor > print selectWarning > except: > + sys.exc_clear() > try: > from twisted.internet import > default as bestreactor > print selectWarning > > > -- > - Norman Rasmussen > - Email: [EMAIL PROTECTED] > - Home page: http://norman.rasmussen.co.za/ > _______________________________________________ > py-transports mailing list > py-transports@blathersource.org > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports