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 mla
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 kno
Michael Droettboom wrote:
[...]
> All this raises a much larger question of whether we want to replace
> font_manager.py with something like fontconfig. There don't appear to
> be Python wrappers for it, but it would eliminate a number of issues
> with font_manager.py : a) it would look up fonts i
I just finished writing code to support scalable mathtext with the Cairo
backend. (The old version rendered the mathtext to bitmaps first).
Mostly straightforward, but I ran into one small snag. It *seems* that
pycairo requires that the fonts it uses are installed and accessible
through fontconf
Ryan May wrote:
>> 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.
I'm a big namespace fan. I'd much rather see us all
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 referen
Tom Holroyd (NIH/NIMH) [E] wrote:
[...]
>
> For the C library you say "man strcpy" or "man erf" and it tells you
> what include file to use to get the definition (function prototype). In
> python you only get the help after you've already imported. But it was
> and still is reasonable to have a
Christopher Barker wrote:
>> http://www.artima.com/weblogs/viewpost.jsp?thread=95863
>
> Thanks
>> (It was in Mike's original message.)
>
> I must have missed that. Guido says:
>
> """
> I've yet to see an extension module using SWIG that doesn't make me
> think it was a mistake to use SWIG ins
Christopher Barker wrote:
> Ryan May wrote:
>>> 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.
>
> I'm a big namesp
Eric Firing wrote:
> Michael Droettboom wrote:
>> I appreciate the way it fits so nicely into C++ ideas about RAII and
>> exceptions -- but if you're not a C++ guy, that pro is probably a con.
> What is RAII?
"Resource Aquisition is Initialization" -- It's a C++ memory management
technique where
Eric Firing wrote:
> I do not think mlab
> should "from numpy import *"; if that is what someone wants, they can do
> it explicitly themselves, very easily. Now, pylab should do something
> like "from mlab import *; from numpy import *; from pyplot import *",
> but mlab should be its own nice,
11 matches
Mail list logo
