Re: [matplotlib-devel] developer policy question

On Fri, Aug 13, 2010 at 1:34 PM, John Hunter wrote: > On Fri, Aug 13, 2010 at 1:26 PM, Benjamin Root wrote: > > Found it. It is solid black. > > Not quite: > In [95]: im = > imread('/home/titan/johnh/Downloads/failed-diff-pcolormesh.png').ravel() > > In [96]: im.max() > Out[96]: 0.039215688 > >

Re: [matplotlib-devel] developer policy question

On Fri, Aug 13, 2010 at 1:34 PM, John Hunter wrote: > On Fri, Aug 13, 2010 at 1:26 PM, Benjamin Root wrote: >> Found it.  It is solid black. > > Not quite: > In [95]: im = > imread('/home/titan/johnh/Downloads/failed-diff-pcolormesh.png').ravel() > > In [96]: im.max() > Out[96]: 0.039215688 > >

Re: [matplotlib-devel] developer policy question

On Fri, Aug 13, 2010 at 1:26 PM, Benjamin Root wrote: > Found it.  It is solid black. Not quite: In [95]: im = imread('/home/titan/johnh/Downloads/failed-diff-pcolormesh.png').ravel() In [96]: im.max() Out[96]: 0.039215688 In [97]: im.min() Out[97]: 0.0 ---

Re: [matplotlib-devel] developer policy question

On Fri, Aug 13, 2010 at 1:18 PM, John Hunter wrote: > On Fri, Aug 13, 2010 at 12:53 PM, Benjamin Root wrote: > > > Where are the difference images saved to? Or do I have to pass an option > to > > matplotlib.test() to generate those? I only have a directory > > FYI, the code is in lib/matplotl

Re: [matplotlib-devel] developer policy question

On Fri, Aug 13, 2010 at 12:53 PM, Benjamin Root wrote: > Where are the difference images saved to?  Or do I have to pass an option to > matplotlib.test() to generate those?  I only have a directory FYI, the code is in lib/matplotlib/testing/compare.py, and the diff images on failure are placed i

Re: [matplotlib-devel] developer policy question

On Fri, Aug 13, 2010 at 12:31 PM, Eric Firing wrote: > On 08/13/2010 07:20 AM, Benjamin Root wrote: > > On Fri, Aug 13, 2010 at 12:11 PM, Eric Firing > > wrote: > > > > On 08/13/2010 06:20 AM, Benjamin Root wrote: > > > > > > > > > On Thu, Aug 12, 20

Re: [matplotlib-devel] developer policy question

On 08/13/2010 07:20 AM, Benjamin Root wrote: > On Fri, Aug 13, 2010 at 12:11 PM, Eric Firing > wrote: > > On 08/13/2010 06:20 AM, Benjamin Root wrote: > > > > > > On Thu, Aug 12, 2010 at 3:58 PM, Eric Firing > >

Re: [matplotlib-devel] developer policy question

On Fri, Aug 13, 2010 at 12:11 PM, Eric Firing wrote: > On 08/13/2010 06:20 AM, Benjamin Root wrote: > > > > > > On Thu, Aug 12, 2010 at 3:58 PM, Eric Firing > > wrote: > > > > On 08/12/2010 09:56 AM, Benjamin Root wrote: > > > > > Btw, the current set of tests

Re: [matplotlib-devel] developer policy question

On 08/13/2010 06:20 AM, Benjamin Root wrote: > > > On Thu, Aug 12, 2010 at 3:58 PM, Eric Firing > wrote: > > On 08/12/2010 09:56 AM, Benjamin Root wrote: > > > Btw, the current set of tests has a failure for testing pcolormesh. > > Wasn't there a change fai

Re: [matplotlib-devel] developer policy question

On Thu, Aug 12, 2010 at 3:58 PM, Eric Firing wrote: > On 08/12/2010 09:56 AM, Benjamin Root wrote: > > > Btw, the current set of tests has a failure for testing pcolormesh. > > Wasn't there a change fairly recently to fix a problem with pcolormesh, > > so that the test image should now be updated

Re: [matplotlib-devel] developer policy question

On 08/12/2010 09:56 AM, Benjamin Root wrote: > Btw, the current set of tests has a failure for testing pcolormesh. > Wasn't there a change fairly recently to fix a problem with pcolormesh, > so that the test image should now be updated? Mike did update the images a couple weeks ago, and when I ru

Re: [matplotlib-devel] developer policy question

On Thu, Aug 12, 2010 at 2:39 PM, John Hunter wrote: > On Thu, Aug 12, 2010 at 2:34 PM, Benjamin Root wrote: > > I am currently working to patch something in colors.py and I am coming > > across a lot of older style code and code that duplicates functionality > that > > can be found in cbook.py (

Re: [matplotlib-devel] developer policy question

On Thu, Aug 12, 2010 at 2:34 PM, Benjamin Root wrote: > I am currently working to patch something in colors.py and I am coming > across a lot of older style code and code that duplicates functionality that > can be found in cbook.py (particularly the type-checking functions).  Is > there a standin

[matplotlib-devel] developer policy question

I am currently working to patch something in colors.py and I am coming across a lot of older style code and code that duplicates functionality that can be found in cbook.py (particularly the type-checking functions). Is there a standing rule that code that we come across should get updated or adap