PythonCOM and --debug
Jesper Eskilson
jojo at virtutech.se
Thu Apr 5 07:29:02 EDT 2001
Hi!
Consider a PythonCOM server implemented as follows:
--- [ cut ] ---
from win32com import universal
from win32com.client import constants
from win32com.client import gencache
from win32com.server.exception import COMException
import win32com.server.register
import winerror
universal.RegisterInterfaces('{1A223A5B-3A79-41DA-A746-639C79B5C397}', 0, 1, 0, ["FooServer"])
class FooServer:
_com_interfaces_ = ['FooServer']
_reg_clsid_ = "{FADA3D76-8525-4A51-876A-1EB39B968F04}"
_reg_progid_ = "My.FooServer"
_reg_desc_ = "FooServer"
_public_methods_ = ['PublicMethod']
def PublicMethod(self):
return winerror.E_NOTIMPL
if __name__ == '__main__':
win32com.server.register.UseCommandLine(FooServer)
--- [ cut ] ---
When I register this server with the --debug option, the client which needs
to talk to the server fails to connect and gets HRESULT=0x80004002. If I
don't register using the --debug option, the client can connect ok.
Any clues as to what the --debug option does to make the client fail to
connect?
Unfortunately, I don't have the source code to the COM-client; it's a third
unreleased third-party product.
Thanks,
/Jesper
--
-------------------------------------------------------------------------
Jesper Eskilson jojo at virtutech.se
Virtutech http://www.virtutech.se
-------------------------------------------------------------------------
More information about the Python-list
mailing list