Re: [PyCrust] C++ "throw" crashes PyCrust instead of triggering python traceback

[Robin D. <ro...@al...>]

[Sorry, I didn't see this message right wawy because of a fault in my 
filters.]

Patrick K. O'Brien wrote:
> "Sebastian Haase" <ha...@ms...> writes:
> 
> 
>>Hi all,
>>I am writing C++ code that I make wrap (using SWIG) so that it's callabl
>>from python.
>>When there is a exception on the C++ level (C++ throw) this should be get
>>converted into an exception on the Python level, that is, I should see a
>>python traceback.  If I run python in the normal terminal window it works
>>like that. Also IDLE behaves well - giving the traceback.
>>
>>PyCrust on Linux used to seg-fault on this (2+ month ago?) but now it works
>>(since PyCrust 0.9 or so) -- THATS THE GOOD NEWS !!
>>But the bad news is that on Windows it crahes -- I get
>>"Runtime Error!  Program: C:\python22\pythonw.exe -- abnormal program
>>termination" -- and then 'OK' closes everything ...
>>Here are the versions I use - I just got it yesterday from wxWindows CVS
>>(2.4 branch)
>>shell.about()
>>Author: "Patrick K. O'Brien <po...@or...>"
>>Py Version: 0.9.2
>>Py Shell Revision: 1.1.2.5
>>Py Interpreter Revision: 1.1.2.2
>>Python Version: 2.2.2
>>wxPython Version: 2.4.1.0p1
>>Platform: win32
> 
> 
> Thanks for the info.  That's the latest version.
> 
> 
>>Please help - or tell me how I can help ;-)
> 
> 
> I wish I knew.  I don't do any work with C++.  Robin, got any ideas
> about this?  Anyone else?  If not, you may want to post something to
> comp.lang.python, since there are many more people there than on this
> list.

Please tell me a bit more about it.  Does the exception work correctly 
on Windows if not run from PyCrust?  What about if it is run from some 
other wxPython app?  Can you extract and show us the code that is 
converting the c++ exception into the Python exception?


-- 
Robin Dunn
Software Craftsman
http://wxPython.org  Java give you jitters?  Relax with wxPython!