Re: [Matplotlib-users] installation problem on Mac

In article , Rebecca Gray wrote: > I am trying to install matplotlib on my Mac OS X 10.6.6. I currently have > Python 2.7.2 installed. I tried installing > ***matplotlib-1.0.1-python.org-32bit-py2.7-macosx10.3.dmg. > The installation appears to run fine, but when I try to import pylab * I am > g

Re: [Matplotlib-users] canvas.draw() + pyqt4 memory leak

On 06/16/2011 04:31 AM, zb wrote: > line 1245 of cbook.py is missing the windows platform. So windows cannot > be tested. > In the development version of mpl it can (I added it--but too recently for it to have gotten into 1.0.1), provided you have the "tasklist" executable, which I think is a fr

Re: [Matplotlib-users] Memory increasing while plotting in loop

Hi Jakob, yes your solution works and is more elegant! See the code at the end of this message. However using the original code with the Agg backend instead of WXAgg also works fine, so there is probably a memory leakage problem with WXAgg (see the post of David and my reply). Thank for your repl

Re: [Matplotlib-users] Memory increasing while plotting in loop

Hi, I'm using WXAgg by default because I developped an application with GUI using wxpython. But in this case indeed I don't need WXAgg and substituting WXAgg by Agg just work fine, both in the code I submitted as example (see the corrected code at the end) and in the one I'm working with. So yes,

Re: [Matplotlib-users] canvas.draw() + pyqt4 memory leak

line 1245 of cbook.py is missing the windows platform. So windows cannot be tested. def report_memory(i=0):  # argument may go away     'return the memory consumed by process'     from subprocess import Popen, PIPE     pid = os.getpid()     if sys.platform=='sunos5':     a2 = Popen('ps -p %d

Re: [Matplotlib-users] canvas.draw() + pyqt4 memory leak

Hi. Sorry but that program does not even run. I am using matplotlib-1.0.1.win32-py2.6.exe It breaks with the error (I had to modified a little to get the full error): UnboundLocalError: local variable 'mem' referenced before assignment Traceback (most recent call last): File... File "C:\Python2

Re: [Matplotlib-users] colorbar() moves to wrong place on subplots_adjust call

On Tue, Jun 14, 2011 at 4:58 AM, Nicholas Devenish wrote: > Is there a way I can avoid or correct this behaviour? It certainly > seems erroneous that using the figure GUI to adjust plot bounds > doesn't work, and is an especially nice way of tweaking for final > plots. > Unfortunately no. This is

Re: [Matplotlib-users] quick documentation fix

Thanks. I fixed it in in the master branch. https://github.com/matplotlib/matplotlib/commit/649df91f8e0bb77687be0711d64201904bcdde67 Regards, -JJ On Wed, Jun 15, 2011 at 7:04 AM, Uri Laserson wrote: > In the Legend Guide: > http://matplotlib.sourceforge.net/users/legend_guide.html > it gives

Re: [Matplotlib-users] Memory increasing while plotting in loop

I can run the script you provided up to 600 without noticing any memory growth (TkAgg backend by default). Using the WxAgg, the memory leak appears. If you don't explicitly need WxAgg, I would recommend using TkAgg, or better Agg if you are not showing the figures. If it is not the case, more expe

Re: [Matplotlib-users] Memory increasing while plotting in loop

Hi, I'm not sure if it helps, but you can try to plot always into the same figure object instead of creating a new one every time you call the plot_density function. I would create one figure in advance and pass this the plot_density method. Within the method set the figure active (pl.figure(f

Re: [Matplotlib-users] Memory increasing while plotting in loop

Hi, http://old.nabble.com/file/p31858795/ErrorMsg.png indeed I forgot to remove these line from previous tests, sorry. However it doesn't affect the code behaviour, the problem remains (it fills the RAM memory and raises a memory error, see img in att.). Alain Davidmh wrote: > > You are im