Problem with loading win32com.client in ActivePython 2.3.2

[Justin Stockton]

I recently upgraded from ActivePython 2.2.2 to ActivePython 2.3.2 and
I'm running into an issue importing the win32com.client module.

Before installing the new version, I made sure to properly remove old
version (as well as the mx libraries I had installed). I then
installed the new version as a user with the Administrator role. I
know I'm technically not supposed to install to a directory with a
space in the name, but it worked fine for ActivePython 2.2.2.

I've included the error message that I get when attempting to import
the win32com.client module.

ActivePython 2.3.2 Build 231 (ActiveState Corp.) based on
Python 2.3.2 (#49, Nov 6 2003, 10:18:20) [MSC v.1200 32 bit (Intel)]
on win32
Type "help", "copyright", "credits" or "license" for more information.Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "C:\Program Files\ActiveState\Python\Lib\site-packages\win32com\client\__
init__.py", line 12, in ?
import dynamic, gencache, pythoncom
File "C:\Program Files\ActiveState\Python\Lib\site-packages\win32com\client\ge
ncache.py", line 623, in ?
__init__()
File "C:\Program Files\ActiveState\Python\Lib\site-packages\win32com\client\ge
ncache.py", line 52, in __init__
Rebuild()
File "C:\Program Files\ActiveState\Python\Lib\site-packages\win32com\client\ge
ncache.py", line 610, in Rebuild
_SaveDicts()
File "C:\Program Files\ActiveState\Python\Lib\site-packages\win32com\client\ge
ncache.py", line 57, in _SaveDicts
raise RuntimeError, "Trying to write to a readonly gencache
('%s')!" \
RuntimeError: Trying to write to a readonly gencache
('C:\DOCUME~1\shiloh\LOCALS
~1\Temp\gen_py\2.3')!

Now the part that weirds me out, is that even though import
win32com.client throws an error, I can do the following.

So I know that everything should be installed correctly.
I'm hoping that someone has seen this before, and can help me out.
Thanks in advance for any help with this issue that is currently
driving me nuts.

- Justin

 

[Trent Mick]

[Justin Stockton wrote]

I recently upgraded from ActivePython 2.2.2 to ActivePython 2.3.2 and
I'm running into an issue importing the win32com.client module.

Justin,

You are right, I see this as well. And the problem is not because you
used a space in your install path. I have opened a bug for this problem
and will be looking at it very soon:
http://bugs.activestate.com/ActivePython/show_bug.cgi?id=28173
Feel free to add yourself to the CC list for this bug to get an update
when it is fixed.

Note that you are using Build 231 which I haven't actually announced
yet . Build 231 upgraded ActivePython's included PyWin32/win32all to
its latest build and obviously I have not sorted out all the issues
there yet.

If you do not depend on having the very latest PyWin32, you may have
more luck with the previous ActivePython 2.3.2 build (Build 230) which
you can find here:
ftp://ftp.activestate.com/ActivePython/windows/2.3/ActivePython-2.3.2-230-win32-ix86.msi

Now the part that weirds me out, is that even though import
win32com.client throws an error, I can do the following.

Actually, that is just a side-effect of the "win32com" module being
_partially_ imported. Python will not try again the second time around.
If you start a new shell and then run that again:

from win32com import client

you will get the same error.

http://aspn.activestate.com/ASPN/do...he-changes-don-t-show-up-why-does-this-happen

Cheers,
Trent