Python ActiveX Scripting interface

Paul Moore paul.moore at uk.origin-it.com
Wed Jun 9 11:37:02 EDT 1999


I've just tried to set up Python on my Windows NT box (NT4 SP4). I
installed Python (1.5.2) and Mark Hammond's Python Win32 extensions
(build 125) with no problems. I ran the ActiveX scripting registration
script, to install the scripting interfaces, but I still have no joy
in trying to use Python as an ActiveX scripting language.

In WSH 2.0, if I specify LANGUAGE="Python", I get a message about that
not being a known language. The Internet Explorer examples fail to
work (with script errors) - I'm using IE5.

I know this is so vague a report as to be pretty much useless - I
can't clarify much at the moment as I'm away from the machine in
question. But I was wondering two things:

1. Is there any reason why the Python script interface would fail to
work with WSH 2.0 or IE5? It seems unlikely, but I suppose it's
possible...

2. Can anybody tell me exactly what I should look for in the registry,
to be sure that Python is registered properly as a scripting host? (I
don't relish trying to understand the Python script that does the
registration...!)

Thanks for any help. When I'm next at the machine in question, I'll
try to isolate the problem a bit better.

Paul Moore.





More information about the Python-list mailing list