> > You know, we are all volunteering our time here on the list to help, > and I think blaming us to not be able to read hundred lines of code is > not productive at all. It's not our side of the task to track whole > parts of programs down. And, usually one has to play with the code > and to run it to see if it fixes the problem! > > You can help improving matplotlib by providing the things the core > developers or experienced Python users like me need to track the error > down inside of matplotlib. > > Friedrich > > P.S.: Try to not think in experts and customers terms. >
I'm sorry you took anything I said as "blame". Not intended that way. Just stating that using figure() and close() resolved the issue. As I look back on the material I've used to learn how to use Matplotlib, they sometimes call these functions and sometimes not. I've concluded that it is required to call these functions. The message to this list is that it *appears* at least to me that it is required to call these functions. Hopefully that will help someone. ------------------------------------------------------------------------------ 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
