Eric Firing wrote:
> Thanks. There were in fact several points of incompatibility with
> Numeric and numarray. (Normally I would have checked this, but I
> slipped up.) I have changed quiver.py and numerix to solve the
> immediate problem, and to slightly reduce the incidence of such
> problem
> "humufr" == humufr <[EMAIL PROTECTED]> writes:
humufr> "should" but sometimes perhaps it's too hard to do
humufr> this. One solution, if the function won't work with
humufr> anything else than numpy, is to print a warning/error
humufr> message for this specific function. Tha
> "Tom" == Tom Denniston <[EMAIL PROTECTED]> writes:
Tom> FigureCanvasAgg seems to make fonts appear much larger that
Tom> FigureCanvasWxAgg. I am trying to get plots generated
Tom> interactively in a wx window to appear the same as those that
Tom> I generate in a no display b
Le vendredi 9 juin 2006 18:30, Christopher Barker a écrit :
> [EMAIL PROTECTED] wrote:
>
> well, anyone using Numeric (or numarray), can just keep on using it for
> a god while. So something that works now should work for a while into
> the future.
"should" but sometimes perhaps it's too hard to d
On 6/9/06, John Hunter <[EMAIL PROTECTED]> wrote:
> the other is that mathtext doesn't recognize \sin, \cos, \exp etc.
> (Edin are you out there? If so, this would be something useful to
> work on).
Yes, I'm alive and well, thank you :).
It's on my radar now.
___
Thanks. There were in fact several points of incompatibility with
Numeric and numarray. (Normally I would have checked this, but I slipped
up.) I have changed quiver.py and numerix to solve the immediate
problem, and to slightly reduce the incidence of such problems in the
future. The real so
