Re: [Matplotlib-users] Error: This application has requested the Runtime to terminate it in an unusual way

[Axel K. <A.K...@gm...>]

Hi John,

>    >> Fatal Python error: PyEval_RestoreThread: NULL tstate This
>    >> application has requested the Runtime to terminate it in an
>    Axel> unusual way.
>    >> Please contact the application's support team for more
>    >> information.
>
>This error has cropped up before in other contexts, always on win32,
>and I think a common cause is when you import the tk backend but do
>not start the tk mainloop (which is what show does), which is what I
>suspect you are doing since this is the default backend on win32.  
>
Yes, that's exactly what's happening. I'm using winXP with matplotlib 
0.65 and Activestate Python 2.3.2

>Does the
>minimal script, which does nothing but "import pylab" replicate the
>problem?
>
>  
>
This replictes the problem:

#!/usr/bin/env python
from pylab import *
rcParams['interactive'] = False
plot([1,2,3])
savefig('bla.ps')

>Do you know that you can run the script with -dPS from the shell to
>switch the backend?  
>
This is not really appropriate for me, since I read some user input and 
decide then (after the script is running) if I produce screen output or 
only a PS file :-(

If you or anyone else finds a solution, please let me know.

Many thanks,
                         Axel