ROTECTED]
> Sent: Thursday, 31 May 2007 1:19 AM
> To: Mark Hammond; python-win32@python.org
> Subject: RE: [python-win32] Win32 COM cache problem
>
>
> That's odd, if I copy the tlb in the current folder then the
> __init__.py is not recreated:
>
> 10:33:14 AM XSI.ex
ngine.
-mab
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Heller
Sent: May 30, 2007 12:08 PM
To: python-win32@python.org
Subject: Re: [python-win32] Win32 COM cache problem
Marc-André Belzile schrieb:
> I dig a bit more and it appears that th
Marc-André Belzile schrieb:
> I dig a bit more and it appears that the python win32 com module requires all
> target typelibs to be in the app current directory. Otherwise the cache is
> systematically re-generated anytime a new scripting engine is created.
>
> Am I doing something wrong ? Than
ond; python-win32@python.org
Subject: Re: [python-win32] Win32 COM cache problem
That's odd, if I copy the tlb in the current folder then the __init__.py is not
recreated:
10:33:14 AM XSI.exe:3896QUERY INFORMATION
C:\Python25\lib\site-packages\win32com\gen_py\__init__.py
Engine->AddTypeLib( theLibGUID, dwLibMajorVersion, dwLibMinorVersion,
SCRIPTTYPELIB_ISCONTROL );
-mab
-Original Message-
From: Mark Hammond [mailto:[EMAIL PROTECTED]
Sent: May 29, 2007 10:24 PM
To: Marc-André Belzile; python-win32@python.org
Subject: RE: [python-win32] Win32 COM cache problem
> I dig
> I dig a bit more and it appears that the python win32 com
> module requires all target typelibs to be in the app current
> directory. Otherwise the cache is systematically re-generated
> anytime a new scripting engine is created.
This should not be the case, and there should be no assumption
I dig a bit more and it appears that the python win32 com module requires all
target typelibs to be in the app current directory. Otherwise the cache is
systematically re-generated anytime a new scripting engine is created.
Am I doing something wrong ? Thanks in advance...
-mab
-Original
