Find why program does not exit after frame is destroyed

wx.Exit() will always force an exit, no matter what, but it may also bypass any wx.EVT_CLOSE handlers you may have added. Also, it does not “exit…the application”. It exits the wxPython app.MainLoop(). Whether or not the Python interpreter is also exited is up to what code you have put after the app.MainLoop() statement.

Package wx

Exit()
Force an exit of the [sic] application. Convenience for wx.GetApp().Exit()”

Ray, your comment is not in the thread--again. Did you really click
on "reply" to the previous message?

There’s also wx.App.ExitMainLoop() which destroys the wxPython’s application object. Not sure if it kills Python application object, too.

···

On Sun, Oct 17, 2010 at 9:49 PM, C M cmpython@gmail.com wrote:

Ray, your comment is not in the thread–again. Did you really click

on “reply” to the previous message?

To unsubscribe, send email to wxPython-users+unsubscribe@googlegroups.com

or visit http://groups.google.com/group/wxPython-users?hl=en

Yes, I really did click the [Reply] button this time to reply.

My only guess is that the Firefox browsers I've used (the latest
versions) to send Gmail is somehow messing things up. Firefox has been
self-updating many times in the last few months. I'm currently using
3.6.10.??.??.??

(This reply was sent using Firefox. I will resend using MS IE as an
experiment.)

···

On Oct 17, 3:49 pm, C M <cmpyt...@gmail.com> wrote:

Ray, your comment is not in the thread--again. Did you really click
on "reply" to the previous message?