[python-win32] f(win32all, COM server, py2exe) continued
Fri, 14 Mar 2003 20:13:03 -0800 (PST)
Wish I had the time or the -foo to do the threadstate stuff, but I've
never used a thread in my life. :-)
And, I'm not in a hurry. I'm willing to stay on 150 as long as it takes,
since that's working.
What I will do is test whatever you have to test. If somebody got this
working already, I could try their stuff out.
--- Mark Hammond <email@example.com> wrote:
> > Now the problem is when I run the sucker, my process (App.exe) hangs,
> > hangs, hangs, hangs, dies. This happens as soon as I do a Dispatch
> > python, or for example a CreateObject in VBA. And it blocks. Fun!
> This will be the thread-state happiness that needs to be done. win32com
> will attempt to acquire the thread lock immediately an object is
> andif this lock is already held, we deadlock.
> There are 2 options, none of which are great:
> * Wait for some threadstate patches to py2exe. I actually know someone
> has managed to get this working, and I am hoping to get patches from him
> * Wait for Python 2.3, where the thread-state should be much easier to
> manage and fix.
> I guess a third option would be the first option done by someone else
Do you Yahoo!?
Yahoo! Web Hosting - establish your business online