On 3/04/2012 2:51 AM, Tim Roberts wrote:
David Manns wrote:We have a scripting engine interface in our application. This works fine for loading/calling VBscript and Javascript scripting engines, but PythonScript fails. Specifically, it fails at : m_pAxsScript->AddNamedItem("application", SCRIPTITEM_NAMEDITEM) where m_pAxsScript is the IActiveScript interface acquired through CoCreateInstance. The hresult returned is: 80004005 which to my mind implies some kind of 'access denied' error.Have you enabled Python as an Active Scripting engine? It's not enabled by default, because there are security issues that couldn't be completely eliminated without disabling parts of the interpreter. See win32comext\axscript\client\pyscript.py.
Actually, it should be enabled by default - it is just that we don't support any of the "safety options" of the active script interfaces. Thus, the end result is that the engine is available in contexts like Windows Scripting Host or ASP, but not in IE.
Mark _______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
