two questions

#1

Okay, here's the patch. I'm also including a quick demo

    > with a button that gets added directly to the canvas.

OK, great. Steve could you take a look at this when you get a minute
and give some feedback about whether you think this is a god idea.

    > On a side note, I can't get the CVS version to work under
    > ipython, and get this error (it was working fine with
    > 0.83.2):
    > ---------------------------------------------------------------------------
    > exceptions.SystemError Traceback (most recent call last)

    > SystemError: Objects/moduleobject.c:48: bad argument to
    > internal function Segmentation fault

Have you done the standard clean install

  > sudo rm -rf build /your/path/to/site-packages/matplotlib
  > sudo python setup.py install

I recently upgraded pycxx in CVS and my first guess is you have some stale
object code lying around.

JDH

#2

Just tried the 'rm -fr ...../site-packages/matplotlib', and I still get the same behavior. Also, if that were the cause, then shouldn't it also crash outside of ipython as well?

John Hunter wrote:

···

"Abraham" == Abraham Schneider <abes@...137...> writes:
           
   > Okay, here's the patch. I'm also including a quick demo
   > with a button that gets added directly to the canvas.

OK, great. Steve could you take a look at this when you get a minute
and give some feedback about whether you think this is a god idea.

   > On a side note, I can't get the CVS version to work under
   > ipython, and get this error (it was working fine with
   > 0.83.2):
   > ---------------------------------------------------------------------------
   > exceptions.SystemError Traceback (most recent call last)

   > SystemError: Objects/moduleobject.c:48: bad argument to
   > internal function Segmentation fault

Have you done the standard clean install

> sudo rm -rf build /your/path/to/site-packages/matplotlib
> sudo python setup.py install

I recently upgraded pycxx in CVS and my first guess is you have some stale
object code lying around.

JDH

-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

#3

Abraham Schneider wrote:

Just tried the 'rm -fr ...../site-packages/matplotlib', and I still get the same behavior. Also, if that were the cause, then shouldn't it also crash outside of ipython as well?

I should note that I'v also seen this same crash with 0.83.2 official.

I haven't bothered to track it down, because I hardly ever use GTK except when testing for problems on the list.

It may not happen outside of ipython, if somehow the crash is triggered by the threading tricks which ipython uses to enable GTK interactive use. Nasty...

Cheers,

f