Just a bad example. I know there are functions that were originally defined in
Matlab and then got rewritten in python, but I've never been clear on which
modules they really live in.
Ryan May wrote:
> Tom Holroyd (NIH/NIMH) [E] wrote:
>> Eric Firing wrote:
>>> Similarly, after dealing with mlab, I would like to simplify pylab.
>>> Right now, we have a horrible tangle of namespaces in pylab. Cleaning
>>> this up will potentially break user code; if a numpy function formerly
>>> could be referenced with three different names and we knock that down to
>>> one, code using the other two will not work. My guess is that in
>>> practice the amount of breakage will be *very* small and easy for users
>>> to deal with.
>> I for one will be happy to change my code; numerical stuff in numpy,
>> plotting stuff in pylab (or pyplot?), though some things like linspace() may
>> be hard to loose; that's really an mlab function and I can import mlab. It
>> probably makes more sense.
>
> I'm not sure if linspace was just a bad example, but it does exist
> within numpy itself.
>
> Ryan
>
--
I say to you: good and evil which would be everlasting- it does not
exist! Of its own accord must it ever overcome itself anew.
-- thus spoke Zarathustra
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
