On Sat, Aug 21, 2010 at 2:08 PM, Eric Firing <efir...@hawaii.edu> wrote: > Mike, John, or anyone else who works directly with Ticks: > > I think you are the only ones who have worked with the code I suggest > changing as in the attached diff. It looks to me like the three *Tick > methods, set_view_interval(), get_minpos(), get_data_interval(), are unused > and unlikely ever to have been or to be used. I particularly object to the > first of these because I don't think a Tick has any business changing the > view interval. The other two look like clutter, harmless except insofar as > they make it harder to understand the code. If some projection actually does > end up needing the functionality in any of these methods, it is still > available via *Tick.axes.xaxis.* etc. > > Am I missing something? If not, I will commit this to the trunk. This is a > case where I think immediate surgery is better than a deprecation process.
I'm OK with removing them, and I don't feel strongly about deprecation with a helpful suggestion or radical mastectomy, though the former seems a little gentler. This should go into the trunk only since it is API breaking. JDH ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
