John Hunter wrote:
> On Tue, Jan 27, 2009 at 3:33 PM, Ryan May wrote:
>> Hi,
>>
>> Do the online docs automatically update themselves from changes in SVN? I
>> thought there was a nightly cron. I made some changes a few days ago (just
>> a few
>> typos) and they haven't shown up online yet. Th
Ryan May wrote:
> John Hunter wrote:
>
>> On Tue, Jan 27, 2009 at 3:33 PM, Ryan May wrote:
>>
>>> Hi,
>>>
>>> Do the online docs automatically update themselves from changes in SVN? I
>>> thought there was a nightly cron. I made some changes a few days ago (just
>>> a few
>>> typos) and
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
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
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. I was just following suit. I can
see where you are coming from
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.
(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 you use it in the
converter implementation is obviously dependent
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