Talk:Matplotlib

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
Start	This article has been rated as Start-class on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.
	This article is supported by WikiProject Software.

Claim of memory leaks

On the article page, I claimed that "as of October 2005, basic plotting commands in Matplotlib suffer from memory leaks." Someone will probably dispute me on that (or perhaps show how it can be avoided). Here's how I tested for memory leaks:

>>> from pylab import *
>>> plot(range(10000), range(10000))
>>> show()
>>> plot(range(10000), range(10000))
>>> plot(range(10000), range(10000))
>>> plot(range(10000), range(10000))
>>> plot(range(10000), range(10000))
>>> plot(range(10000), range(10000))
>>> plot(range(10000), range(10000))

Note how the process memory usage increases continuously with each new plot command. - Connelly 00:58, 14 October 2005 (UTC)[reply]

Yep, someone will dispute you:-). matplotlib by default does not clear the previous plot, so you are adding many equivalent lines to the same plot. memory leaks in matplotlib have been hunted down agressively for many releases: there are FAQs about them and unit tests to detect them. To prevent the so-called leak in your example, set the hold rc property to False., or plor with plot(x,y,hold=False).

May I humbly suggest that you learn matplotlib, read it FAQ, and post to the user's list before posting disparaging comments on the wikipedia. Your, the matplotlib author, John Hunter.

I tried hold(False) and plot(..., hold=False), to no avail. See bug 1366913. Anyway, I probably shouldn't have been complaining about memory leaks in a pre-1.0 library on Wikipedia, so apologies for that, it was rude. - Connelly 09:30, 5 February 2006 (UTC)[reply]

The above is original research81.174.255.69 (talk) 13:25, 29 June 2009 (UTC)[reply]

Sales pitch?

This article seems a whole lot like a sales pitch to me... -Kevin Holzer

Python 2.6

I am using mathplot with 2.6.2 and it just works (tm) —Preceding unsigned comment added by 91.97.79.3 (talk) 12:39, 1 July 2009 (UTC)[reply]

Python 3

The current version of the library (1.1.1) has been ported to python 3.

http://pythonsprints.com/2011/04/8/matplotlib-python-3-thanks-cape-town-group/ — Preceding unsigned comment added by 46.11.12.15 (talk) 13:37, 28 July 2012 (UTC)[reply]

"Matplotlib" or "matplotlib"?

Shouldn't it be "Matplotlib" (not "matplotlib")? --Mortense (talk) 08:04, 5 June 2016 (UTC)[reply]