matplotlib-users Mailing List for matplotlib

On 2004年12月18日, John Hunter apparently wrote:
> Can we get some positive confirmation from other
> win32 users that 0.65 is working for them?
No problems yet on Win2000 Pro or Win XP.
(I have only run a few scripts since my upgrade,
but they all worked.)
Alan Isaac

>>>>> "Gary" == Gary <pa...@in...> writes:
 Gary> I changed axes.py to remove 'min' from the 'from numerix
 Gary> import ...' line.
 Gary> Now it chokes on the very next line, from numerix import max
 Gary> as nxmax
Let's be systematic. From the python shell, what happens when you do
 >>> import Numeric, MLab
 >>> Numeric.__version__
 >>> from MLab import min, max
 >>> import matplotlib
 >>> matplotlib.__version__
 >>> from matplotlib.numerix import min, max
This will help narrow down whether it's a matplotlib or Numeric
problem. Check the reported version numbers to make sure the numeric
upgrade went as expected.
Do you have only one python installed on your system?
 Gary> Am I the only one suffereing from this? Isn't this impossible?
My win32 setup appears to be working fine. It's clearly not
impossible <wink>. Can we get some positive confirmation from other
win32 users that 0.65 is working for them?
JDH

>>>>> "Axel" == Axel Kowald <A.K...@gm...> writes:
 Axel> Hello, I have the following small problem when terminating a
 Axel> matplotlib script. Basically I do the following
 Axel> (interactive set to False): from pylab import *
 Axel> plot([1,2,3]) savefig('bla.ps')
 Axel> Now, this script does produce the PS file but then
 Axel> terminates with the error message:
 >> 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. My
guess is the bug will go away if you call "show" at the end of the
script, but then you'll get the GUI window in addition to the ps file.
I'm not sure if there is a fix for this. Basically, you want to
create postscript output using the tk backend without having the tk
window popup. Perhaps Todd has some ideas about what to do with tk
internals to avoid this problem, but I don't know offhand. I'll try
and take a look next week when I have access to a win32 box. Does the
minimal script, which does nothing but "import pylab" replicate the
problem?
Do you know that you can run the script with -dPS from the shell to
switch the backend? Then you'll get the PS, no GUI popup, no error,
and you won't have to alter your script. You can also place an rc
file in the directory where the script resides and make PS the default
backend. When you want to switch to GUI mode, you can replace the
backend parameter with TkAgg again. But you'll need the show in that
case.
If you get any additional information from some of the tests suggested
above, let me know, because as I said this PyEval_RestoreThread has
popped up in many contexts, including multiple calls to show or not
calling it at all. I would like to fix these problems if possible so
that it "just works".
See related threads
http://sourceforge.net/mailarchive/message.php?msg_id=10271482
http://sourceforge.net/mailarchive/message.php?msg_id=10114470
JDH

Hello,
I have the following small problem when terminating a matplotlib script.
Basically I do the following (interactive set to False):
from pylab import *
plot([1,2,3])
savefig('bla.ps')
Now, this script does produce the PS file but then terminates with the 
error message:
 >Fatal Python error: PyEval_RestoreThread: NULL tstate
 >This application has requested the Runtime to terminate it in an 
unusual way.
 >Please contact the application's support team for more information.
I know that I could use the PS backend which avoids this problem, but I 
want to be flexible and either generate a PS file or some screen output 
and so I keep the default backend.
Since the script actually does what it should do the question is 
somewhat aesthetical:
How can I avoid this error message ?
Many thanks,
 Axel Kowald

John Hunter wrote:
>>>>>>"Gary" == Gary <pa...@in...> writes:
>>>>>> 
>>>>>>
>
> Gary> ---------------------------------------------------------------------
> Gary> C:\Python23\Lib\site-packages\matplotlib\examples>python
> Gary> Python 2.3.4 (#53, May 25 2004, 21:17:02) [MSC v.1200 32 bit
> Gary> (Intel)] on win32 Type "help", "copyright", "credits" or
> Gary> "license" for more information.
> >>>> from matplotlib.numerix import min
> Gary> Traceback (most recent call last): File "<stdin>", line 1,
> Gary> in ? ImportError: cannot import name min
> Gary> ----------------------------------------------------------------
>
>It looks like your Numeric install is screwed up. Remove
>site-packages Numeric to be on the safe side and grab the latest
>release for your python version at 
>
> http://sourceforge.net/projects/numpy
>
>reinstall and see if that fixes your problem. Let me know...
>
>JDH
>
> 
>
I'm sorry to report no change. I uninstalled Numeric and matplotlib, 
and reinstalled both, and nothing has changed. Am I the only one 
suffereing from this? Isn't this impossible?
I tried this several times. I uninstalled using the Control Panel Add 
and Remove feature, and then trashed the remaining directory. I 
searched the registry for lurking remnants (there was a mention of an 
uninstaller and .matplotlibrc. that's all. I left those entries 
alone.) I checked .matplotlibrc... nothing obviously unusual, just 
numerix:Numeric. A week ago I did a virus scan on the whole system, and 
ran spybot. (I'll probably run those again tonight for good measure.) 
The version of Numeric that I installed is 23.6, the latest. I'm using 
python 2.3.4
I changed axes.py to remove 'min' from the 'from numerix import ...' line.
Now it chokes on the very next line,
from numerix import max as nxmax
... and happy holidays.
-gary