Re: [matplotlib-devel] overridding builtin variables in pylab

[Norbert N. <Nor...@gm...>]

I fear that this "fix" will rather add to the general confusion than lighten 
it. First doing "from ... import *" and then reverting it partly really seems 
like a bad idea. The cleaner solution would be to fix Numeric/numarray in 
such a way that the replacement min/max/round/... retain the complete 
original functionality of the builtins only extending them to new types. 
Independent of pylab, there obviously is a bug in the underlying libraries 
which should not be obscured but solved.

I already hate the current situation as it is: Both, SciPy and matplotlib, are 
based upon Numeric/numarray, but then they change and extend its behaviour in 
subtle ways so that - in the end - the user is completely confused. If there 
is a bug or a missing feature in the array library, it should be fixed there. 
Having arrays behave similar but slightly different in SciPy, matplotlib and 
numarray/Numeric should be avoided by all means.

-- 
_________________________________________Norbert Nemec
         Bernhardstr. 2 ... D-93053 Regensburg
     Tel: 0941 - 2009638 ... Mobil: 0179 - 7475199
           eMail: <No...@Ne...>

-- 
_________________________________________Norbert Nemec
         Bernhardstr. 2 ... D-93053 Regensburg
     Tel: 0941 - 2009638 ... Mobil: 0179 - 7475199
           eMail: <No...@Ne...>