Re: [Matplotlib-users] "from pylab import *" will no longer override min() and max()

[Perry G. <pe...@st...>]

On Jan 24, 2005, at 10:09 AM, John Hunter wrote:
> So the two questions are: 1) are people in favor of this change? and

I haven't given lengthy thought, but yes, I think it is probably a good
idea. The only counterargument is that something like making them 
available
in pylab is that it guards a bit against possible reorganization of the
modules and could potentially shield users against that. One view of 
pylab
is that it provides a more stable interface to what is underneath. If 
there
are items that are pretty fixed in their design, perhaps they belong 
(here
or in another related module)

> 2) if so, what should matplotlib.pylab export?  Only symbols defined
> therein?  Or perhaps add a few for backward compatibility?  
> Specifically
> I'm wondering if matplotlib.pylab should continue to export: cm.jet,
> cm.gray, etc, date2num, num2date, drange, and perhaps the *Locator and
> *Formatter symbols from matplotlib.ticker and matplotlib.dates?  I
> don't suppose it's possible to "warn on import", eg warning
> "matplotlib.pylab import of date2num is deprecated, please use
> matplotlib.dates instead".  One could write wrappers for this, I know,
> but is there some import wizardry which supports this?
>
I think one could overload the import mechanism to handle this, but I'm
thinking that it is probably not worth the downside of messing with
the import mechanism.

Perry