matplotlib-devel Mailing List for matplotlib

Mark Roddy wrote:
> On Wed, Apr 28, 2010 at 12:30 PM, Mark Roddy <mar...@gm...> wrote:
>> On Wed, Apr 28, 2010 at 11:49 AM, Michael Droettboom <md...@st...> wrote:
>>> Thanks. Yes, I would consider tabs a bug. A patch is very welcome.
>>>
[...]
> 
> I added a patch to the tracker:
> https://sourceforge.net/tracker/?func=detail&aid=2993733&group_id=80706&atid=560720
> 
Your patch has been applied. Thank you.
Eric
> -Mark

On Wed, Apr 28, 2010 at 12:30 PM, Mark Roddy <mar...@gm...> wrote:
> On Wed, Apr 28, 2010 at 11:49 AM, Michael Droettboom <md...@st...> wrote:
>> Thanks. Yes, I would consider tabs a bug. A patch is very welcome.
>>
>> Mike
>>
>> Mark Roddy wrote:
>>>
>>> I'm trying to resolve an issue with my source base that uses
>>> matplotlib. We run our CI tests with the '-tt' option which causes
>>> errors on mixed tabs/spaces, and this has caused our builds to start
>>> failing since the inclusion of matploblib on one of our projects due
>>> to mixed use of tab and space characters in some of the pure python
>>> code. We're using v0.99.0 and I count 43 occurences of tab characters
>>> across 5 files in this release. I checked out the trunk and found 26
>>> occurrences across 9 files. I determined these via:
>>> find -name \*.py|xargs grep -P '\t', and
>>> find -name \*.py|xargs grep -Pl '\t'
>>>
>>> According to the style guide[1], use of tabs is a bug, but I wanted to
>>> inquire if this standard is still in place before filing a bug report.
>>> I can provide a patch if so (which should only consist of running
>>> reindent).
>>>
>>> Thanks,
>>> Mark
>>>
>>> 1:
>>> http://matplotlib.sourceforge.net/devel/coding_guide.html#naming-spacing-and-formatting-conventions
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> Matplotlib-devel mailing list
>>> Mat...@li...
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>
>>
>> --
>> Michael Droettboom
>> Science Software Branch
>> Operations and Engineering Division
>> Space Telescope Science Institute
>> Operated by AURA for NASA
>>
>>
>
> Thanks Mike. I'll open a bug with the patch attached.
>
> -Mark
>
I added a patch to the tracker:
https://sourceforge.net/tracker/?func=detail&aid=2993733&group_id=80706&atid=560720
-Mark

On Wed, Apr 28, 2010 at 11:49 AM, Michael Droettboom <md...@st...> wrote:
> Thanks. Yes, I would consider tabs a bug. A patch is very welcome.
>
> Mike
>
> Mark Roddy wrote:
>>
>> I'm trying to resolve an issue with my source base that uses
>> matplotlib. We run our CI tests with the '-tt' option which causes
>> errors on mixed tabs/spaces, and this has caused our builds to start
>> failing since the inclusion of matploblib on one of our projects due
>> to mixed use of tab and space characters in some of the pure python
>> code. We're using v0.99.0 and I count 43 occurences of tab characters
>> across 5 files in this release. I checked out the trunk and found 26
>> occurrences across 9 files. I determined these via:
>> find -name \*.py|xargs grep -P '\t', and
>> find -name \*.py|xargs grep -Pl '\t'
>>
>> According to the style guide[1], use of tabs is a bug, but I wanted to
>> inquire if this standard is still in place before filing a bug report.
>> I can provide a patch if so (which should only consist of running
>> reindent).
>>
>> Thanks,
>> Mark
>>
>> 1:
>> http://matplotlib.sourceforge.net/devel/coding_guide.html#naming-spacing-and-formatting-conventions
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>
> --
> Michael Droettboom
> Science Software Branch
> Operations and Engineering Division
> Space Telescope Science Institute
> Operated by AURA for NASA
>
>
Thanks Mike. I'll open a bug with the patch attached.
-Mark

Thanks. Yes, I would consider tabs a bug. A patch is very welcome.
Mike
Mark Roddy wrote:
> I'm trying to resolve an issue with my source base that uses
> matplotlib. We run our CI tests with the '-tt' option which causes
> errors on mixed tabs/spaces, and this has caused our builds to start
> failing since the inclusion of matploblib on one of our projects due
> to mixed use of tab and space characters in some of the pure python
> code. We're using v0.99.0 and I count 43 occurences of tab characters
> across 5 files in this release. I checked out the trunk and found 26
> occurrences across 9 files. I determined these via:
> find -name \*.py|xargs grep -P '\t', and
> find -name \*.py|xargs grep -Pl '\t'
>
> According to the style guide[1], use of tabs is a bug, but I wanted to
> inquire if this standard is still in place before filing a bug report.
> I can provide a patch if so (which should only consist of running
> reindent).
>
> Thanks,
> Mark
>
> 1: http://matplotlib.sourceforge.net/devel/coding_guide.html#naming-spacing-and-formatting-conventions
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

I'm trying to resolve an issue with my source base that uses
matplotlib. We run our CI tests with the '-tt' option which causes
errors on mixed tabs/spaces, and this has caused our builds to start
failing since the inclusion of matploblib on one of our projects due
to mixed use of tab and space characters in some of the pure python
code. We're using v0.99.0 and I count 43 occurences of tab characters
across 5 files in this release. I checked out the trunk and found 26
occurrences across 9 files. I determined these via:
find -name \*.py|xargs grep -P '\t', and
find -name \*.py|xargs grep -Pl '\t'
According to the style guide[1], use of tabs is a bug, but I wanted to
inquire if this standard is still in place before filing a bug report.
 I can provide a patch if so (which should only consist of running
reindent).
Thanks,
Mark
1: http://matplotlib.sourceforge.net/devel/coding_guide.html#naming-spacing-and-formatting-conventions

I think this is due to improper use of the path.simplify_threshold value 
in the simplification code. It should have been squared since it's used 
in a 2-dimensional euclidean distance calculation.
I have made the change to SVN r8280 and updated a few of the unit tests 
that are now more accurate than they used to be. As a workaround (if 
you're not running from SVN and don't want to rebuild), you can set the 
rcParam path.simplify_threshold to 0.01, rather than 0.1.
Mike
Michael Droettboom wrote:
> Thanks. I can confirm this with today's SVN. I'm looking into the cause.
>
> Mike
>
> On 04/25/2010 07:11 PM, Tom Aldcroft wrote:
> 
>> import numpy
>> import matplotlib
>> matplotlib.use('Agg')
>> import matplotlib.pyplot as plt
>>
>> y = numpy.array([
>> 4., 2., 2., 3., 3., 2., 2., 6., 6., 5., 5., 4., 4.,
>> 7., 7., 2., 2., 4., 4., 2., 2., 2., 2., 4., 4., 4.,
>> 4., 4., 4., 7., 7., 3., 3., 5., 5., 4., 4., 5., 5.,
>> 4., 4., 7., 7., 6., 6., 2., 2., 2., 2., 5., 5., 4.,
>> 4., 4., 4., 6., 6., 3., 3., 4., 4., 3., 3., 2., 2.,
>> 3., 3., 4., 4., 4., 4., 4., 4., 6., 6., 5., 5., 4.,
>> 4., 7., 7., 3., 3., 4., 4., 4., 4., 5., 5., 4., 4.,
>> 7., 7., 3., 3., 4., 4., 4., 4., 6., 6., 4., 4., 4.,
>> 4., 4., 4., 2., 2., 5., 5., 6., 6., 3., 3., 5., 5.,
>> 4., 4., 0., 0., 5., 5., 1., 1., 4., 4., 5., 5., 4.])
>>
>> plt.figure(figsize=(7,4))
>> plt.plot(y)
>> plt.savefig('test.png')
>>
>> plt.xlim(-12000, 8274)
>> plt.savefig('test_panned.png')
>> 
>> 
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Hi all,
I've come across a memory leak when saving multiple figures in a row.
The figure contains a single pcolormesh artist, which I need to
rasterize in my application. However, turning on rasterization causes
a memory leak.The attached script reproduces the problem; swap out the
commented section at the bottom to eliminate memory growth for each
new figure.
I'm not sure what the cause is, though to toss one idea out, might it
have to do with a references that aren't cleaned up from the
rasterizing part of the mixed-mode renderer?
Tested on Mac OS X and, thanks to Patrick Marsh, on Windows.
Thanks,
Eric