I probably found where the problem resides. As it is a wxPython+Matplotlib
issue, I will send the mail to both newsgroups.
The reason why my application does not terminates correctly on Windows 2000
while it terminates correctly on Windows XP does not depend on Windows version,
but on Matplotlib. I am not 100% sure, because here I only have (at the
moment) Windows XP, but I found a difference between 2 Matplotlib installations
On XP, I have Matplotlib 0.73 prerelease (that WAS a prerelease 1 months
ago, nearly), while on Windows 2000 I have Matplotlib 0.74.
Well, I am using the WXAgg backend. By looking at backend_wx.py in 0.73pre
(XP), I see that lines 116-117 are commented. These lines are:
# wxapp = wxPySimpleApp()
While on Matplotlib 0.74 (2000) they are NOT commented. Well, in my app
I don't need to initialize the wx.App() when calling plot/figure/Matplotlib
things, because my app has ALREADY initialized the wx.App().
If I use Matplotlib (without wxPython) I will just add:
MyApp = wx.PySimpleApp()
Before using any Matplotlib command.
Is there a reason why these lines were commented on 0.73pre and now they
are not? Robin/John, could it be that the reason for which my application
does not return under Windows 2000?
Thanks to you all.
It's incredible... after having found that my application correctly
terminates if I add the line:
on Windows XP, I am UNABLE to terminate it on Windows 2000. The main
is correctly destroyed, together with its children, but there is still
alive that prevents Python to correctly finish and returning to me the
of the DOS console.
The wxPython version is the same, the Python version is the same... the
only differences between the 2 PC is the Windows version (XP=work, 2000=don't
work) and the PC performances (XP=1GB RAM, 2000=528MB RAM).
I used Spy++ and its friends and, after my app terminates, on 2000 there
is still a window opened. This window has no class information, no particular
ID, only a size and position elements. There is no reason why the application
behavior should be different.
I don't even know which question I would formulate to you NG, it is a
this continuous error-checking for a window/frame/panel that I didn't
and that wxPython thinks is still alive (only on Windows 2000).
If you can create a small sample that shows the problem I can run it
under the debugger to see if I can spot what's going on.
http://wxPython.org Java give you jitters? Relax with wxPython!