Re: [matplotlib-devel] backend_macosx framework check fails with 64bit Python

To avoid having to import MacOS, I've implemented the MacOS.WMAvailable() function in src/_macosx.m. The updated version of backend_macosx.py doesn't import MacOS; see revision 8625 in trunk. --Michiel. --- On Tue, 8/10/10, Derek Homeier wrote: > From: Derek Homeier > Subject: [matplotlib-de

Re: [matplotlib-devel] Handle 'none' as edgecolor for bar()

On Mon, Aug 9, 2010 at 10:02 AM, Ben North wrote: > >> I tried to use "edgecolor = 'none'" in a call to bar(), hoping to get no > >> border to the bars, but instead got no bars at all. > > > > Just to note, the documentation does specify a difference between None > and > > 'none'. None means to

Re: [matplotlib-devel] Handle 'none' as edgecolor for bar()

Ben Root: >Ben North: >> Same kind of thing with >> the kwarg 'color' instead of 'edgecolor', which is also fixed in my >> second recent email. > > Looking through the code for bar(), I see the same thing occurs for the > 'color' keyword argument. So I guess we should fix that as well. Yes, the s

Re: [matplotlib-devel] Handle 'none' as edgecolor for bar()

On Thu, Aug 12, 2010 at 10:13 AM, Ben North wrote: > Ben Root: > >Ben North: > >> Same kind of thing with > >> the kwarg 'color' instead of 'edgecolor', which is also fixed in my > >> second recent email. > > > > Looking through the code for bar(), I see the same thing occurs for the > > 'color'

Re: [matplotlib-devel] Handle 'none' as edgecolor for bar()

On 08/12/2010 06:09 AM, Benjamin Root wrote: > On Thu, Aug 12, 2010 at 10:13 AM, Ben North > wrote: > > Ben Root: > >Ben North: > >> Same kind of thing with > >> the kwarg 'color' instead of 'edgecolor', which is also fixed in my > >> second re

[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

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

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] Handle 'none' as edgecolor for bar()

On Thu, Aug 12, 2010 at 12:37 PM, Eric Firing wrote: > On 08/12/2010 06:09 AM, Benjamin Root wrote: > > On Thu, Aug 12, 2010 at 10:13 AM, Ben North > > wrote: > > > > Ben Root: > > >Ben North: > > >> Same kind of thing with > > >> the kwarg 'color

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] Handle 'none' as edgecolor for bar()

On 08/12/2010 10:40 AM, Benjamin Root wrote: [...] > > > > >>> mcolor.colorConvertor.to_rgba_array('none') > > array([], shape=(0, 4), dtype=float64) > > > > >>> mcolor.colorConvertor.to_rgba_array(['none']) > > array([[ 0., 0., 0., 0.]]) > > > > >>> mcolo