Re: [matplotlib-devel] online docs updating?

2009-01-28 Thread Ryan May
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

Re: [matplotlib-devel] online docs updating?

2009-01-28 Thread Michael Droettboom
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

[matplotlib-devel] Updated units.ConversionInterface

2009-01-28 Thread James Evans
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

Re: [matplotlib-devel] Updated units.ConversionInterface

2009-01-28 Thread Eric Firing
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

Re: [matplotlib-devel] Updated units.ConversionInterface

2009-01-28 Thread James Evans
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

Re: [matplotlib-devel] Updated units.ConversionInterface

2009-01-28 Thread John Hunter
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.

Re: [matplotlib-devel] Updated units.ConversionInterface

2009-01-28 Thread Drain, Theodore R
(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

Re: [matplotlib-devel] Updated units.ConversionInterface

2009-01-28 Thread John Hunter
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