On Feb 1, 2005, at 11:10 PM, Richard Jones wrote:
I've just switched from running py2app with -A to not using it. After fleshing out the "includes" option so that my required modules were included, I finallly got the app to start up. It promptly quits, with the following message:
Fatal Python error: PyThreadState_Get: no current thread Abort trap
My app is a simple GUI thing which controls Zope through the zdaemon.zdctl module. It's attached. The Zope libs (and some supporting libs) are installed in the app's Resources folder in a "runtime" subdirectory (historical name, will eventually change to Zope ;)
As I mentioned, this works OK when I invoke py2app with -A but it breaks when I run it for real.
I'm not using threads in my app, but Zope does use threads when it's running. The invocation of the zdaemon.zdctl code should not create any threads that I'm aware of. I'm currently working through a process of elimination to see whether I can narrow down to a particular suspect.
Does anyone have any ideas what might cause this?
Could be a lot of things. I can't really start to guess unless I can see it.
-bob
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
