matplotlib-users Mailing List for matplotlib

Maybe, the situation could be somewhat relaxed by uncluttering pylab:
Currently, pylab.py does two things:
* give a stateful matlab like interface to the object-oriented matplotlib 
plotting library
* pull together all kinds of namespaces.
What about pulling all the plotting routines into a separate file that can be 
included by anyone who just wants the comfortable plotting commands without 
all the other namespace cluttering. pylab itself would then only contain lots 
of imports and all the namespace mangling.
For me personally, this would be the solution. I use matplotlib for plotting 
only and for my purpose , simple plotting interface from pylab is much nicer 
than the full object oriented interface.
For numerics, however, I would prefer to go as pythonic as possible without 
any compromises for matlab similarity.
Cleanly dividing the two purposes of matplotlib (nice plotting and matlab 
similarity) would certainly help matters.
-- 
_________________________________________Norbert Nemec
 Bernhardstr. 2 ... D-93053 Regensburg
 Tel: 0941 - 2009638 ... Mobil: 0179 - 7475199
 eMail: <No...@Ne...>

>>>>> "danny" == danny shevitz <dan...@ya...> writes:
 danny> my comments on modules being exposed appear to have fallen
 danny> into a vacuum. I still ask if "from matplotlib import *"
 danny> should expose the time module or the sys module?
Hi Danny,
Apparently your voice has escaped the void! I added the __all__
attribute to the pylab module to restrict the symbols it exports
strictly to matplotlib and numerix symbols, which should protect you
from these kids of unexpected effects.
Cheers,
JDH