Re: [python-win32] [pywin32 extensions] Traceback error on running startup script

2012-04-02 Thread Maggard, Eric
Hi Mark, Thanks for the message. Nope, I am not using Unicode, so I guess that is where the problem is. I did get 2.7 running and initializing, but I am having a problem getting the interactive window to show, open a script, or create new script. I tried to run the startup.py and intpyapp.py

[python-win32] IActiveScript::AddNamedItem fails with exception

2012-04-02 Thread David Manns
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 i

Re: [python-win32] IActiveScript::AddNamedItem fails with exception

2012-04-02 Thread Tim Roberts
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_

Re: [python-win32] IActiveScript::AddNamedItem fails with exception

2012-04-02 Thread Mark Hammond
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",

Re: [python-win32] IActiveScript::AddNamedItem fails with exception

2012-04-02 Thread Mark Hammond
On 3/04/2012 1:09 AM, 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