Followup...
solved the previously mentionned "import" problem.
But hunting the segfault problem, perhaps it's related to my "static" build?
Check out the following:
In SWIG-generated core.py:
...
class App(wx.PyApp):
def RedirectStdio ...
if filename: ...
else: ...
_sys.stdout = _sys.stderr = self.stdioWin
self.stdioWin is <core.PyOnDemandOutputWindow instance at 0x40ffae0c>
but for some reason executing that last line gives
(process:842): GLib-GObject-CRITICAL **: gtype.c:1807:g_type_register_static(): initialization assertion failed, use g_type_init() prior to this function
I don't quite know what the fix is at this moment, but the hunt continues...
Vio
Followup...
solved the previously mentionned "import" problem.
But hunting the segfault problem, perhaps it's related to my "static" build?
Check out the following:
In SWIG-generated core.py:
...
class App(wx.PyApp):
def RedirectStdio ...
if filename: ...
else: ...
_sys.stdout = _sys.stderr = self.stdioWin
self.stdioWin is <core.PyOnDemandOutputWindow instance at 0x40ffae0c>
but for some reason executing that last line gives
(process:842): GLib-GObject-CRITICAL **: gtype.c:1807:g_type_register_static(): initialization assertion failed, use g_type_init() prior to this function
The errors are probably happening prior to this and just being flushed at this point as that line doesn't do anything with the UI at all. However I would reccommend that in your situation that you do *not* let the stdio be redirected until you get all the kinks worked out with your embedding task. Just let the output go to the console instead, otherwise the simple act of printing something or getting a traceback could cause more errors that hide the true problems.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!