# Python ActiveX Scripting Demonstation

Congratulations on installing the Python ActiveX Scripting Engine

### Object model

Except as described below, the object module exposed should be similar to that exposed by Visual Basic, etc. Due to the nature of ActiveX Scripting, the details for each host are different, but Python should work "correctly".

The object model exposed via Python for MSIE is not as seamless as VB. The biggest limitation is the concept of a "local" namespace. For example, in VB, you can code `text="Hi there"`, but in Python, you must code `MyForm.ThisButton.Text="Hi There"`. See the foo2 sample for futher details.

### Known bugs and problems

- This release seems to have broken Aaron's mouse-trace sample. No idea why, and looking into it.

- Support for Active Debugging is only partially implemented.

- Certain events fire twice. Specifically in IE3, the Window_OnLoad handler is called twice.

- Builtin objects such as MARQUEE are giving me grief. Objects accessed via forms are generally no problem.

- The spruuids sample AXScript engine from Microsoft currently does not work. This is being investigated.

- Support for Active Server Pages is very limited - ASP removes whitespace from all code, making it pretty hard to use. In effect, you are limited to non-indented code. One work-around is to create a Python module with the real code, and simply import and call that module from the ASP page.

- If you are trying to use Python with the Windows Scripting Host, you must have a recent version of WSH. It definately works with build 419 and later. Also note that .pys files may not be fully registered - you may need to explicitely specify either cscript.exe or wscript.exe on the command line.