johnf wrote: > On Thursday 19 March 2009 02:49:59 pm Pedro Vale de Gato wrote: >> Would setting a sys.excepthook solve the wxPython event loop not ending >> problem? > > Could you explain a little more. Larry is running into what I think you are > talking about. In the VFP world I'd call that a "Dangling" referrence that > caused the program to think there was still a variable/reference that needed > to be released.
In Pedro's case, an exception was raised during the update cycle. This exception happened in a combo box because the Value wasn't present in the Keys. This exception, being unhandled, prevented any other controls from being updated, so it resulted in some controls having data from the current record, and some from the prior. In general, wxPython doesn't exit the main event loop after an unhandled exception, resulting in the above behavior. In my opinion, the correct behavior after an unhandled exception mirror's Python's behavior: exit the program. Paul _______________________________________________ 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/[email protected]
