Okay. Done.
--James
> -Original Message-
> From: John Hunter [mailto:jdh2...@gmail.com]
> Sent: Wednesday, January 28, 2009 11:46 AM
> To: James Evans
> Cc: Eric Firing; matplotlib development list
> Subject: Re: [matplotlib-devel] Updated units.ConversionInterface
&
On Wed, Jan 28, 2009 at 3:16 PM, Drain, Theodore R
wrote:
> (nitpick mode on)
>
> Saying they can ignore it more easily seems like a bit of a stretch to me.
> If you're writing a converter you MUST include the axis in the function
> signature since callers will be passing it in. Whether or not
ll be wrong in
some cases (just probably not the case they test with).
Ted
> -Original Message-
> From: John Hunter [mailto:jdh2...@gmail.com]
> Sent: Wednesday, January 28, 2009 11:46 AM
> To: James Evans
> Cc: matplotlib development list; Eric Firing
> S
On Wed, Jan 28, 2009 at 1:19 PM, James Evans wrote:
> Eric,
>
> I was looking at it from the perspective of most of the other API calls
> throughout matplotlib have the Axes or Axis as the first
> argument. Typically this is because it is what wants the work to be done or
> is being worked on.
s Evans
> Cc: 'matplotlib development list'
> Subject: Re: [matplotlib-devel] Updated units.ConversionInterface
>
> James Evans wrote:
> > All,
> >
> > I have just submitted an updated units.ConversionInterface. For each of
> > the static methods it now
James Evans wrote:
> All,
>
> I have just submitted an updated units.ConversionInterface. For each of the
> static methods it now takes the invoking Axis instance
> as a parameter. I have updated the appropriate calling functions. This
> allows the DateConverter to now guarantee that the defa
All,
I have just submitted an updated units.ConversionInterface. For each of the
static methods it now takes the invoking Axis instance
as a parameter. I have updated the appropriate calling functions. This allows
the DateConverter to now guarantee that the default
axes no longer attempts to
