COM exceptions

[Mark Hammond]

You really need to look into the object.  There is nothing special
about a COM exception - all it means is that a COM method returned a
non-zero result, and this is transformed into a Python exception.
There is no code in the PythonCOM support that could explain this...

Mark.

"sven" <sashaNOsaSPAM at ofoto.com.invalid> wrote in message
news:05108cf7.cd1ab828 at usw-ex0102-015.remarq.com...
>
> A question for any and all Python/COM experts:
>
>      I'm writing a multi-threaded app (under WinNT using the
threading
> module) that makes heavy use of a third party COM component.
> Occasionally the component will throw an OLE Error, which bubbles up
to
> my code as a pywintypes.com_error.
> I can't figure out how to gracefully handle these things. When any
> thread encounters one of these, *all* the threads stop (however, the
> main interpreter thread does not exit). I've tried looking for dead
> threads and restarting them (or replacing them with new ones with
the
> same target), but apparently these 'stopped' threads are still
> considered alive.
> I'm not sure if this is a threading issue, a COM issue or some
fiendish
> combination of the two.
>
> Any thoughts?
>
> Thanks for your time.
>
> Sasha
>
>
>
> * Sent from RemarQ http://www.remarq.com The Internet's Discussion
Network *
> The fastest and easiest way to search and participate in Usenet -
Free!
>