This seems to occur due to errornous referencing of wxPython components in non-GUI threads. I never thought that this crashes the interpreter as well, but that seems to comply with the specs, sorry.
This seems to occur due to errornous referencing of wxPython components in non-GUI threads. I never thought that this crashes the interpreter as well, but that seems to comply with the specs, sorry.