It seems to be working now. Thanks!
This is a perfect example of quick response. I keep telling people
that, sure, the scientific python suite has occasional bugs, but the
community is *very* responsive. This is a perfect example. Thanks
to everybody that helped,
-Rob
> Rob, you shoul
John Hunter wrote:
> On 7/13/07, Andrew Straw <[EMAIL PROTECTED]> wrote:
>> grr. that's probably my fault. I just fiddled with the definition of
>> npy. I tested this on linux and thought I copied it pretty directly from
>> numpy, so I assumed it would work elsewhere, but it's not. I'll see what
>>
On 7/13/07, Andrew Straw <[EMAIL PROTECTED]> wrote:
> grr. that's probably my fault. I just fiddled with the definition of
> npy. I tested this on linux and thought I copied it pretty directly from
> numpy, so I assumed it would work elsewhere, but it's not. I'll see what
> I can do...
It amy also
grr. that's probably my fault. I just fiddled with the definition of
npy. I tested this on linux and thought I copied it pretty directly from
numpy, so I assumed it would work elsewhere, but it's not. I'll see what
I can do...
Rob Hetland wrote:
> First of all, Qt4 does appear to work fine.
>
> S
First of all, Qt4 does appear to work fine.
Second. I am trying to recompile, and I get the error attached
below. Somebody had mentioned needing a recent version of gcc. Is
this the problem here, or is it another bug?
-Rob
gcc -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4
This looks like that was introduced by a patching error when fixing the
Tk save figure bug recently. The bug tracker added an extraneous
newline to my patch submitted as a comment. (That's the last time I do
that ;)
http://sourceforge.net/tracker/index.php?func=detail&aid=1716732&group_id=807
On Jul 13, 2007, at 9:14 AM, John Hunter wrote:
>
> Try importing these packages individually
>
> import matplotlib._image
> import matplotlib._transforms
>
> #one of these three depending on which numerix package you are using
> import matplotlib.backends._na_backend_agg # for numarray
> imp
FWIW, I'm able to reproduce this here. I have a hunch it may be related
to my recent Tk memory leak "improvements". I'll look into this further
and get back soon.
Cheers,
Mike
John Hunter wrote:
> On 7/13/07, Rob Hetland <[EMAIL PROTECTED]> wrote:
>
>> Nope -- the same occurs in the regula
On 7/13/07, Rob Hetland <[EMAIL PROTECTED]> wrote:
>
> Nope -- the same occurs in the regular terminal, so it's not
> iPython's fault.
>
> Also, although I though I remembered this happening with qt4 (as
> posted below), I do not seem to be able to reproduce this now..
>
> Also, clearing and closin
Nope -- the same occurs in the regular terminal, so it's not
iPython's fault.
Also, although I though I remembered this happening with qt4 (as
posted below), I do not seem to be able to reproduce this now..
Also, clearing and closing the figure works fine -- only clicking it
away triggers
On 7/12/07, Rob Hetland <[EMAIL PROTECTED]> wrote:
>
> I recently updated matplotlib, and I am now getting a bus error when
> plotting (any command) after I have already closed a matplotlib
> window. I can open as many windows as I want, but the first plot
> command executed after closing any wind
I recently updated matplotlib, and I am now getting a bus error when
plotting (any command) after I have already closed a matplotlib
window. I can open as many windows as I want, but the first plot
command executed after closing any window results in a bus error.
Relavent things:
OS: Mac
12 matches
Mail list logo
