Re: [python-win32] vb errors from Python COM object now include the traceback lines

2012-04-20 Thread Lloyd Kvam
On Fri, 2012-04-20 at 15:52 +1000, Mark Hammond wrote: > On 20/04/2012 8:30 AM, Lloyd Kvam wrote: > > On Thu, 2012-04-19 at 16:32 -0400, Lloyd Kvam wrote: > >> I am hoping one of you can point me in the right direction. My > >> alternative appears to be (painfully) writing some VB code to discard

Re: [python-win32] vb errors from Python COM object now include the traceback lines

2012-04-19 Thread Mark Hammond
On 20/04/2012 8:30 AM, Lloyd Kvam wrote: On Thu, 2012-04-19 at 16:32 -0400, Lloyd Kvam wrote: I am hoping one of you can point me in the right direction. My alternative appears to be (painfully) writing some VB code to discard the traceback lines from Err.Description. Hrm - I thought it had

Re: [python-win32] vb errors from Python COM object now include the traceback lines

2012-04-19 Thread Lloyd Kvam
On Thu, 2012-04-19 at 16:32 -0400, Lloyd Kvam wrote: > I am hoping one of you can point me in the right direction. My > alternative appears to be (painfully) writing some VB code to discard > the traceback lines from Err.Description. I read more carefully through Python Programming on Win32 and

[python-win32] vb errors from Python COM object now include the traceback lines

2012-04-19 Thread Lloyd Kvam
I am upgrading an old windows application from Python 2.4 to Python 2.6. The application is written in portable Python. A GUI interface was created by using Visual Basic (VB 6) and a Python module that wraps the application as a COM object. With python 2.4 (and pywin32-210) exceptions resulted in