Using py2exe to wrap a service?

[Tim Golden]

[MaR]

| I do not call pythoncom.CoInitialize ()  as I tend to expect a module
| wrapping COM stuff to do that. 

Hmmm. A slightly philosophical point. As the author of
the said module, I think I'd have said that the other
way round: I do not call CoInit... because I expect a
user of the module *who needs to involve threading*
to do that. However, I'm quite happy to call it willy-nilly
as long as there's no overhead. But I'm afraid my
knowledge of the interaction of COM with threading
is slim and mostly anecdotal.

| Some further info that may be of interest:
| python 2.4.3
| active_directory 0.4
| py2exe 0.6.5
| pywin32 208
| The Service code is taken from MyService.py supplied with py2exe as a
| sample.

All that looks good enough.

Is it possible for you to include the CoInit... call
anyway, simply as a test to see if it is the problem.
It might not be, in which case the point is moot.
(At least in this case)

If you don't get much help on this list, might
be worth moving the discussion over to the python-win32
list. I'm sure many people (like myself) watch both, but
there may be some who don't follow this list, but
do watch the -- lower traffic -- win32 list.

TJG

________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________