Ok, i found my error. It was due to some invalids flags during compilation. Now my module is working for both standalone python 32/64, or PyInstaller.
Sorry for the mess, Mathieu Le jeudi 31 mai 2012 20:57:59 UTC+2, Mathieu Virbel a écrit : > > Actually, it seem that my module crash as soon as Py_InitModule() is > called. Dunno why yet. Adding the PyEval_InitThreads doesn't change > anything. So i might be wrong on that one. > Will back after investigation. > > Le jeudi 31 mai 2012 16:15:15 UTC+2, Martin Z a écrit : >> >> Could you fork pyinstaller submit a merge request? >> >> That could make it clear what you exactly mean. >> >> Is this the default behavior that should be available in pyinstaller? >> >> Any code to reproduce this failure? >> >> Mathieu Virbel píše v Čt 31. 05. 2012 v 06:38 -0700: >> > >> > Hi guys, >> > >> > I think i got an issue with custom extension that use Python threads. >> > I've a module bootstrap that contain python code using threads API. If >> > i do: $ python >>> import bootstrap -> no crash, everything works. >> > >> > But if i use PyInstaller, i got: Fatal Python error: >> > PyThreadState_Get: no current thread Abort trap: 6 >> > >> > After looking at the source/common/launch.c, it seem like the threads >> > support is not initialized: Py_Initialize(); is not, no >> > PyEval_InitThreads(); >> > >> > Would it be possible to add it as an option somewhere ? By default, >> > the python interpreter is doing it. >> > >> > Mathieu >> >> -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To view this discussion on the web visit https://groups.google.com/d/msg/pyinstaller/-/qAyzw55oZzIJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyinstaller?hl=en.
