Problem with loading win32com.client in ActivePython 2.3.2

Trent Mick trentm at ActiveState.com
Wed Nov 12 18:55:44 CET 2003


[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.
> 
> >>> from win32com import client
> >>>

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/docs/ActivePython/2.3.2/faq/programming.html#when-i-edit-an-imported-module-and-reimport-it-the-changes-don-t-show-up-why-does-this-happen

Cheers,
Trent

-- 
Trent Mick
TrentM at ActiveState.com





More information about the Python-list mailing list