I'm looking for the official view of what should be happening.
Do I have to call pythoncom.CoInitialize() for all but the
main thread or is the win32com code supposed to handle this
behind the scenes
pythoncom is not documented in the PythonWin32Extensions help
with ActiveState Python 202.
BArry
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Syver
> Enstad
> Sent: 02 April 2001 07:27
> To: 'Barry Scott'
> Cc: '[EMAIL PROTECTED]'
> Subject: RE: CoInitialize not called on new thread
>
>
> Call CoInitialize in the new thread maybe... ;-)
>
> Like this: pythoncom.CoInitialize()
>
> > -----Original Message-----
> > From: Barry Scott [mailto:[EMAIL PROTECTED]]
> > Sent: Sunday, April 01, 2001 11:03 PM
> > To: [EMAIL PROTECTED]
> > Subject: CoInitialize not called on new thread
> >
> >
> > We started to see errors using win32com in new python thread.
> > The error is CoInitialize has not been called.
> >
> > How can I force win32com to CoInitialize a new python thread?
> >
> > BArry
> >
> > _______________________________________________
> > ActivePython mailing list
> > [EMAIL PROTECTED]
> > http://listserv.ActiveState.com/mailman/listinfo/activepython
> >
> _______________________________________________
> ActivePython mailing list
> [EMAIL PROTECTED]
> http://listserv.ActiveState.com/mailman/listinfo/activepython
>
>
_______________________________________________
ActivePython mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/activepython
