matplotlib-devel Mailing List for matplotlib

Manuel,
Thank you.
I will look at this ASAP, but it might not be right away. Just to be 
safe, if you haven't heard from me by Friday send me a message off the list.
Manuel Metz wrote:
> Okay, I changed from npy.asarray -> npy.ma.array and checked that it 
> works. I also added a doc. The patch as well as an example code and its 
> output are attached.
> 
> Please note that the example actually call ax.step directly instead of 
> using the pylab interface; I guess this has to be added (boilerplate.py?)
Yes, I can take care of that. No problem.
Eric
> 
> Manuel
> 
> Eric Firing wrote:
>>
>>
>> Manuel Metz wrote:
>>> May I ask again: Is there any interest in a step-plotting function?
>> Yes, so thanks for taking the initiative and for being persistent.
>>>
>>> If so, who will commit the patch? Do I have to add more myself 
>>> (documentation for sure needs to be added, what else ?)
>> Please add a docstring and a simple demo suitable for the examples 
>> subdirectory. I will commit the patch, or some modification of it.
>>>
>>> Manuel
>>>
>>> Manuel Metz wrote:
>>>> Hi,
>>>> okay, I have added a keyword 'where' as suggested. I also now 
>>>> changed the way the incoming data is converted. I took this from the 
>>>> axes.pie() function. I don't know much about the unit types yet :-(
>>>>
>>>> Concerning masked arrays: Do I have to consider something special 
>>>> there?
>> I think that if you change the npy.asarray to npyma.array, and 
>> similarly for the zeros(), that will provide basic masked array 
>> support. Please look at masked_demo.py for an example of the use of 
>> masked arrays. (It is very artificial, of course. A typical use case 
>> for masked arrays is when you have a data stream with some bad points 
>> that you want to edit out, but you want to keep the array dimensions 
>> unchanged. In the case of a line plot or step plot, you want the line 
>> to break at the missing point to show that a point has been removed.)
>>
>> Eric
>>
>>>>
>>>> Manuel
>>>>
>>>> Ted Drain wrote:
>>>>> At 10:36 AM 8/14/2007, Eric Firing wrote:
>>>>>> Ted Drain wrote:
>>>>>>> Manuel,
>>>>>>> We do plots like this all the time. One thing we've found that's 
>>>>>>> nice to have is a keyword that controls when the increase in y 
>>>>>>> happens. We use a step style keyword that can be 'pre' (go up 
>>>>>>> then right), 'post' (go right then up), and 'mid' (right 0.5, up, 
>>>>>>> right 0.5).
>>>>>> Good idea.
>>>>>>> Regarding your patch, you might want to check other areas in MPL 
>>>>>>> for data processing examples. I could be wrong but I'm not sure 
>>>>>>> you can assume that incoming data is a float. Some of the unit 
>>>>>>> conversion examples or the line collection code might have better 
>>>>>>> examples.
>>>>>> Incoming data can be any numeric type, but it ends up getting 
>>>>>> converted to the default float type (not float32) internally.
>>>>>>
>>>>>> Whenever possible, it is good to support masked array input.
>>>>> Agreed - but the way the patch was written, I don't think it will 
>>>>> support anything but float (especially not the unit types).
>>>>>
>>>>>> Eric
>>>>>>> Ted
>>>>>>> At 07:59 AM 8/14/2007, Manuel Metz wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I have created a patch against latest svn that adds a function 
>>>>>>>> step to the axes class to plot step-functions ;-) It's really 
>>>>>>>> simple but nice ... Any interest in adding this?
>>>>>>>>
>>>>>>>> Manuel
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Index: axes.py
>>>>>>>> ===================================================================
>>>>>>>> --- axes.py (revision 3709)
>>>>>>>> +++ axes.py (working copy)
>>>>>>>> @@ -4995,6 +4995,18 @@
>>>>>>>> steps=[1, 2, 
>>>>>>>> 5, 10],
>>>>>>>> integer=True))
>>>>>>>> return im
>>>>>>>> +
>>>>>>>> + def step(self, x, y, *args, **kwargs):
>>>>>>>> + x2 = npy.zeros((2*len(x)), npy.float32)
>>>>>>>> + y2 = npy.zeros((2*len(x)), npy.float32)
>>>>>>>> +
>>>>>>>> + x2[0::2] = x
>>>>>>>> + x2[1::2] = x
>>>>>>>> +
>>>>>>>> + y2[1::2] = y
>>>>>>>> + y2[2::2] = y[:-1]
>>>>>>>> +
>>>>>>>> + self.plot(x2, y2, *args, **kwargs)
>>>>>>>>
>>>>>>>> class SubplotBase:
>>>>>>>> """
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------- 
>>>>>>>>
>>>>>>>> This SF.net email is sponsored by: Splunk Inc.
>>>>>>>> Still grepping through log files to find problems? Stop.
>>>>>>>> Now Search log events and configuration files using AJAX and a 
>>>>>>>> browser.
>>>>>>>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>>>>>>>> _______________________________________________
>>>>>>>> Matplotlib-devel mailing list
>>>>>>>> Mat...@li...
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>>>>> ------------------------------------------------------------------------ 
>>>>>>>
>>>>>>> ------------------------------------------------------------------------- 
>>>>>>>
>>>>>>> This SF.net email is sponsored by: Splunk Inc.
>>>>>>> Still grepping through log files to find problems? Stop.
>>>>>>> Now Search log events and configuration files using AJAX and a 
>>>>>>> browser.
>>>>>>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>>>>>>>
>>>>>>> ------------------------------------------------------------------------ 
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Matplotlib-devel mailing list
>>>>>>> Mat...@li...
>>>>>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>>>
>>>>> ------------------------------------------------------------------------ 
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------- 
>>>>>
>>>>> This SF.net email is sponsored by: Splunk Inc.
>>>>> Still grepping through log files to find problems? Stop.
>>>>> Now Search log events and configuration files using AJAX and a 
>>>>> browser.
>>>>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------ 
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Matplotlib-devel mailing list
>>>>> Mat...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>> ------------------------------------------------------------------------ 
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------ 
>>>>
>>>>
>>>> ------------------------------------------------------------------------- 
>>>>
>>>> This SF.net email is sponsored by: Splunk Inc.
>>>> Still grepping through log files to find problems? Stop.
>>>> Now Search log events and configuration files using AJAX and a browser.
>>>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>>>>
>>>>
>>>> ------------------------------------------------------------------------ 
>>>>
>>>>
>>>> _______________________________________________
>>>> Matplotlib-devel mailing list
>>>> Mat...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>
>>> ------------------------------------------------------------------------- 
>>>
>>> This SF.net email is sponsored by: Splunk Inc.
>>> Still grepping through log files to find problems? Stop.
>>> Now Search log events and configuration files using AJAX and a browser.
>>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>>> _______________________________________________
>>> Matplotlib-devel mailing list
>>> Mat...@li...
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 
> ------------------------------------------------------------------------
> 
> Index: axes.py
> ===================================================================
> --- axes.py	(revision 3720)
> +++ axes.py	(working copy)
> @@ -4987,7 +4987,54 @@
> steps=[1, 2, 5, 10],
> integer=True))
> return im
> + 
> + def step(self, x, y, *args, **kwargs):
> + '''
> + STEP(x, y, *args, **kwargs)
> + 
> + Make a step plot. The args and keyword args to step are the same
> + as the args to plot. See help plot for more info.
> + 
> + Additional keyword args for step:
> + 
> + * where: can be 'pre', 'post' or 'mid'. Determines where the
> + step occurs.
> + '''
> + 
> + where = kwargs.pop('where', 'pre')
> + 
> + if not iterable(x): x = npy.ma.array([x]).astype(npy.float32)
> + else: x = npy.ma.array(x).astype(npy.float32)
> + 
> + if not iterable(y): x = npy.ma.array([y]).astype(npy.float32)
> + else: y = npy.ma.array(y).astype(npy.float32)
> + 
> + if where=='pre':
> + x2 = npy.ma.zeros((2*len(x)-1,), npy.float32)
> + y2 = npy.ma.zeros((2*len(y)-1,), npy.float32)
> + 
> + x2[0::2], x2[1::2] = x, x[:-1]
> + y2[0::2], y2[1:-1:2] = y, y[1:]
> 
> + elif where=='post':
> + x2 = npy.ma.zeros((2*len(x)-1,), npy.float32)
> + y2 = npy.ma.zeros((2*len(y)-1,), npy.float32)
> + 
> + x2[::2], x2[1:-1:2] = x, x[1:]
> + y2[0::2], y2[1::2] = y, y[:-1]
> + 
> + elif where=='mid':
> + x2 = npy.ma.zeros((2*len(x),), npy.float32)
> + y2 = npy.ma.zeros((2*len(y),), npy.float32)
> + 
> + x2[1:-1:2] = 0.5*(x[:-1]+x[1:])
> + x2[2::2] = 0.5*(x[:-1]+x[1:])
> + x2[0], x2[-1] = x[0], x[-1]
> + 
> + y2[0::2], y2[1::2] = y, y
> + 
> + return self.plot(x2, y2, *args, **kwargs)
> +
> class SubplotBase:
> """
> Emulate matlab's(TM) subplot command, creating axes with
> 
> 
> ------------------------------------------------------------------------
> 
> import matplotlib.numerix as npy
> from pylab import *
> 
> x = npy.arange(1.,10.)
> y = arange(1.,10.)
> x[4] += 0.4
> 
> fig = figure()
> ax = fig.gca()
> 
> ax.step(x,y, where='post')
> 
> y += 1.
> ax.step(x,y,where='pre')
> 
> y += 1.5
> ax.step(x,y,where='mid')
> 
> xlim(0,10)
> ylim(-1,13)
> 
> show()
> 
> 
> ------------------------------------------------------------------------
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Darren Dale wrote:
> On Monday 20 August 2007 10:18:27 am Michael Droettboom wrote:
>> On a related note, there was a recent thread on matplotlib-users about
>> usetex being a global setting:
>>
>> http://www.mail-archive.com/mat...@li.../msg04101
>> .html
>>
>> I'm concerned about consistency and/or redundancy between this and the
>> new markup kwarg. I don't know whether or not "usetex" being
>> "all-or-nothing" is desirable. But we could meet in the middle by doing
>> one of the following:
>>
>> a) only send text to LaTeX for rendering when text.usetex=True and
>> markup="tex". (Which makes usetex=True behave a little more like
>> usetex=False).
> 
> This seems like a bad idea. If I want to use tex as my text layout engine, now 
> I have two settings to keep track of. We'll get lots of posts asking why 
> latex is not being used when usetex is True.
I agree with this point. My counter-worry is that people may be 
surprised when their dollar signs behave differently when usetex is on 
or off. Maybe people don't change that setting all that often in 
practice, though... We could (and I'm not necessarily advocate this), 
pre-process the string sent to LaTeX when usetex is True and markup == 
'plain', so that the dollar signs are escaped (and will appear as dollar 
signs in the output).
>> b) add another value to markup, to render text with LaTeX. (If we
>> do, I would suggest changing the kwarg to "text_renderer" and having the
>> values be "normal", "mathtext" and "latex" or something)
> 
> This seems reasonable. Although, if we make it so latex can be used to layout 
> some text but not others, I worry that we will get no end of posts 
> complaining about how the latex fonts dont match the mathtext or normal 
> fonts.
Agreed.
>> c) make markup="tex" be all-or-nothing as well (that is, keep the
>> rcParam, but drop the kwarg.) With this flag, you're basically saying
>> "I know how to deal with $'s".
>>
>> b) is probably the most flexible (maybe too flexible, as I can't see why
>> one would want to use all three types of rendering in the same plot).
>> a) and b) would break backward compatibility with 0.90.1, while c) would
>> not.
>>
>> Any thoughts?
> 
> I think b) fits best. Maybe backward compatibility can be maintained. usetex 
> would be deprecated, and would set the text_renderer rcParam to latex when 
> True.
That seems like a good approach, if we go with option b).
> Or does 0.90.1 already have the markup kwarg?
The markup kwarg is only a couple weeks old.
> Again, there must be a 
> way. The new validation mechanism in rcParams (not traits, the stuff I did 
> right before traits) could probably provide a route for transition without 
> actually breaking anything.
Good point.
> I am pretty busy this week at work, and will be 
> on vacation for 11 days starting August 24, just letting you know.
Thanks. I don't think there's a huge rush to decide this (the 
implementation should be straightforward no matter what we decide). But 
it would make sense to sort this out before the next release.
Cheers,
Mike

On Monday 20 August 2007 10:18:27 am Michael Droettboom wrote:
> On a related note, there was a recent thread on matplotlib-users about
> usetex being a global setting:
>
> http://www.mail-archive.com/mat...@li.../msg04101
>.html
>
> I'm concerned about consistency and/or redundancy between this and the
> new markup kwarg. I don't know whether or not "usetex" being
> "all-or-nothing" is desirable. But we could meet in the middle by doing
> one of the following:
>
> a) only send text to LaTeX for rendering when text.usetex=True and
> markup="tex". (Which makes usetex=True behave a little more like
> usetex=False).
This seems like a bad idea. If I want to use tex as my text layout engine, now 
I have two settings to keep track of. We'll get lots of posts asking why 
latex is not being used when usetex is True.
> b) add another value to markup, to render text with LaTeX. (If we
> do, I would suggest changing the kwarg to "text_renderer" and having the
> values be "normal", "mathtext" and "latex" or something)
This seems reasonable. Although, if we make it so latex can be used to layout 
some text but not others, I worry that we will get no end of posts 
complaining about how the latex fonts dont match the mathtext or normal 
fonts.
> c) make markup="tex" be all-or-nothing as well (that is, keep the
> rcParam, but drop the kwarg.) With this flag, you're basically saying
> "I know how to deal with $'s".
>
> b) is probably the most flexible (maybe too flexible, as I can't see why
> one would want to use all three types of rendering in the same plot).
> a) and b) would break backward compatibility with 0.90.1, while c) would
> not.
>
> Any thoughts?
I think b) fits best. Maybe backward compatibility can be maintained. usetex 
would be deprecated, and would set the text_renderer rcParam to latex when 
True. Or does 0.90.1 already have the markup kwarg? Again, there must be a 
way. The new validation mechanism in rcParams (not traits, the stuff I did 
right before traits) could probably provide a route for transition without 
actually breaking anything. I am pretty busy this week at work, and will be 
on vacation for 11 days starting August 24, just letting you know.
Darren

Hi All-
FYI, I am seeing the same problem on intel OSX 10.4.10
Andrew
Eric Firing wrote:
> Rob, Mike,
> 
> What this implies to me is that either there is a problem with the code 
> that is generating afmdict (and I did not change that code, I just 
> caused it to be invoked when the fontManager instance is created.), or 
> there is a problem with some .afm files on Rob's machine.
> 
> I really don't know how to troubleshoot it beyond this.
> 
> (As a separate issue, I probably I should change font_manager.py so that 
> if the rcParams value below was changed since the cache was made, it 
> will be rebuilt with the new value.)
> 
> Eric
> 
> Rob Hetland wrote:
>> On Aug 14, 2007, at 1:55 PM, Eric Firing wrote:
>>
>>> rcParams['pdf.use14corefonts']
>> Indeed, reversing this value fixes the problem.
>>
>> My value had been set to False.
>> 	pdf.use14corefonts : True
>> in the mplrc file works with the latest revision.
>>
>> -r
>>
>> ----
>> Rob Hetland, Associate Professor
>> Dept. of Oceanography, Texas A&M University
>> http://pong.tamu.edu/~rob
>> phone: 979-458-0096, fax: 979-845-6331
>>
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc.
>> Still grepping through log files to find problems? Stop.
>> Now Search log events and configuration files using AJAX and a browser.
>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@pu...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/

Okay, I changed from npy.asarray -> npy.ma.array and checked that it 
works. I also added a doc. The patch as well as an example code and its 
output are attached.
Please note that the example actually call ax.step directly instead of 
using the pylab interface; I guess this has to be added (boilerplate.py?)
Manuel
Eric Firing wrote:
> 
> 
> Manuel Metz wrote:
>> May I ask again: Is there any interest in a step-plotting function?
> Yes, so thanks for taking the initiative and for being persistent.
>>
>> If so, who will commit the patch? Do I have to add more myself 
>> (documentation for sure needs to be added, what else ?)
> Please add a docstring and a simple demo suitable for the examples 
> subdirectory. I will commit the patch, or some modification of it.
>>
>> Manuel
>>
>> Manuel Metz wrote:
>>> Hi,
>>> okay, I have added a keyword 'where' as suggested. I also now changed 
>>> the way the incoming data is converted. I took this from the 
>>> axes.pie() function. I don't know much about the unit types yet :-(
>>>
>>> Concerning masked arrays: Do I have to consider something special there?
> I think that if you change the npy.asarray to npyma.array, and similarly 
> for the zeros(), that will provide basic masked array support. Please 
> look at masked_demo.py for an example of the use of masked arrays. (It 
> is very artificial, of course. A typical use case for masked arrays is 
> when you have a data stream with some bad points that you want to edit 
> out, but you want to keep the array dimensions unchanged. In the case 
> of a line plot or step plot, you want the line to break at the missing 
> point to show that a point has been removed.)
> 
> Eric
> 
>>>
>>> Manuel
>>>
>>> Ted Drain wrote:
>>>> At 10:36 AM 8/14/2007, Eric Firing wrote:
>>>>> Ted Drain wrote:
>>>>>> Manuel,
>>>>>> We do plots like this all the time. One thing we've found that's 
>>>>>> nice to have is a keyword that controls when the increase in y 
>>>>>> happens. We use a step style keyword that can be 'pre' (go up 
>>>>>> then right), 'post' (go right then up), and 'mid' (right 0.5, up, 
>>>>>> right 0.5).
>>>>> Good idea.
>>>>>> Regarding your patch, you might want to check other areas in MPL 
>>>>>> for data processing examples. I could be wrong but I'm not sure 
>>>>>> you can assume that incoming data is a float. Some of the unit 
>>>>>> conversion examples or the line collection code might have better 
>>>>>> examples.
>>>>> Incoming data can be any numeric type, but it ends up getting 
>>>>> converted to the default float type (not float32) internally.
>>>>>
>>>>> Whenever possible, it is good to support masked array input.
>>>> Agreed - but the way the patch was written, I don't think it will 
>>>> support anything but float (especially not the unit types).
>>>>
>>>>> Eric
>>>>>> Ted
>>>>>> At 07:59 AM 8/14/2007, Manuel Metz wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I have created a patch against latest svn that adds a function 
>>>>>>> step to the axes class to plot step-functions ;-) It's really 
>>>>>>> simple but nice ... Any interest in adding this?
>>>>>>>
>>>>>>> Manuel
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Index: axes.py
>>>>>>> ===================================================================
>>>>>>> --- axes.py (revision 3709)
>>>>>>> +++ axes.py (working copy)
>>>>>>> @@ -4995,6 +4995,18 @@
>>>>>>> steps=[1, 2, 5, 
>>>>>>> 10],
>>>>>>> integer=True))
>>>>>>> return im
>>>>>>> +
>>>>>>> + def step(self, x, y, *args, **kwargs):
>>>>>>> + x2 = npy.zeros((2*len(x)), npy.float32)
>>>>>>> + y2 = npy.zeros((2*len(x)), npy.float32)
>>>>>>> +
>>>>>>> + x2[0::2] = x
>>>>>>> + x2[1::2] = x
>>>>>>> +
>>>>>>> + y2[1::2] = y
>>>>>>> + y2[2::2] = y[:-1]
>>>>>>> +
>>>>>>> + self.plot(x2, y2, *args, **kwargs)
>>>>>>>
>>>>>>> class SubplotBase:
>>>>>>> """
>>>>>>>
>>>>>>> ------------------------------------------------------------------------- 
>>>>>>>
>>>>>>> This SF.net email is sponsored by: Splunk Inc.
>>>>>>> Still grepping through log files to find problems? Stop.
>>>>>>> Now Search log events and configuration files using AJAX and a 
>>>>>>> browser.
>>>>>>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>>>>>>> _______________________________________________
>>>>>>> Matplotlib-devel mailing list
>>>>>>> Mat...@li...
>>>>>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>>>> ------------------------------------------------------------------------ 
>>>>>>
>>>>>> ------------------------------------------------------------------------- 
>>>>>>
>>>>>> This SF.net email is sponsored by: Splunk Inc.
>>>>>> Still grepping through log files to find problems? Stop.
>>>>>> Now Search log events and configuration files using AJAX and a 
>>>>>> browser.
>>>>>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>>>>>>
>>>>>> ------------------------------------------------------------------------ 
>>>>>>
>>>>>> _______________________________________________
>>>>>> Matplotlib-devel mailing list
>>>>>> Mat...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>>
>>>> ------------------------------------------------------------------------ 
>>>>
>>>>
>>>> ------------------------------------------------------------------------- 
>>>>
>>>> This SF.net email is sponsored by: Splunk Inc.
>>>> Still grepping through log files to find problems? Stop.
>>>> Now Search log events and configuration files using AJAX and a browser.
>>>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>>>>
>>>>
>>>> ------------------------------------------------------------------------ 
>>>>
>>>>
>>>> _______________________________________________
>>>> Matplotlib-devel mailing list
>>>> Mat...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>> ------------------------------------------------------------------------
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> ------------------------------------------------------------------------- 
>>>
>>> This SF.net email is sponsored by: Splunk Inc.
>>> Still grepping through log files to find problems? Stop.
>>> Now Search log events and configuration files using AJAX and a browser.
>>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Matplotlib-devel mailing list
>>> Mat...@li...
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc.
>> Still grepping through log files to find problems? Stop.
>> Now Search log events and configuration files using AJAX and a browser.
>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel