Adding a close() at the end didn't do anything - still get the same message.
stetrick wrote: > > I removed and reinstalled everything, and I'm still getting it. > > I am using the multiprocessing lib. Each process then produces a graph > with matplotlib, which is only done with Savefig (never interactively > displaced during the creation process). I have nothing special in the > configuration - just using the 64-bit windows defaults. > > Probably some setup thing. > > > Christoph Gohlke wrote: >> >> >> >> >>>> Christoph >>> >>> I thought that was fixed: >>> http://sourceforge.net/tracker/?func=detail&aid=3015013&group_id=80706&atid=560720 >>> >>> Eric >>> >> >> Yes the bug is fixed. If the program is terminated properly. However, >> you can still crash the Python interpreter if you close or kill the >> console window while the following script is running. >> >> python -c"from matplotlib import pyplot;pyplot.hot();input()" >> >> -- >> Christoph >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> _______________________________________________ >> Matplotlib-users mailing list >> Matplotlib-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/matplotlib-users >> >> > > -- View this message in context: http://old.nabble.com/Fatal-Python-Error-with-64-bit-versions-tp29392620p29413159.html Sent from the matplotlib - users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
