Well... I've added a print statement as the first and last line in every method in the OutlookAddin class in addin.py. It appears that it's calling and returning from __init__ successfully, but it crashes before getting to the print statement in any other method. I wonder if it's a problem with the COM interface with the win32com module.
Greg -----Original Message----- From: spambayes-bounces+greg=bahns....@python.org [mailto:spambayes-bounces+greg=bahns....@python.org] On Behalf Of Greg Bahns Sent: Monday, June 07, 2010 10:10 PM To: Mark Hammond Cc: spambayes@python.org Subject: Re: [Spambayes] Win7 and Outlook 2010 64-bit What would you recommend for a debugging environment? -----Original Message----- From: Mark Hammond [mailto:mhamm...@skippinet.com.au] Sent: Monday, June 07, 2010 9:26 PM To: Greg Bahns Cc: spambayes@python.org Subject: Re: [Spambayes] Win7 and Outlook 2010 64-bit On 8/06/2010 11:21 AM, Greg Bahns wrote: > I was able to capture the error below when trying to enable the add-in. > Looks like write permissions in the win32com folder. I changed > directory to the parent folder "C:\\Program > Files\\Python26\\lib\\site-packages\\win32com\\gen_py\\" and ran this: > > C:\Program Files\Python26\Lib\site-packages> *C:\Program > Files\Python26\Lib\site-packages* > > After this, I seem to have gotten past the write permissions, because > I see the dicts.dat file now, with the current date and time. Right - permissions is one reason Python doesn't install in Program Files by default. > > But now it just crashes Outlook. I'm going to try to figure out what's > happening. Any troubleshooting tips would be appreciated. I'm a > developer, but haven't done Python in years, and have never done > Outlook add-ins. For starters it would help to know what the entry > point is when Outlook tries to load the add-in. In the Outlook add-in > dialog it shows that the add-in is pythoncom26.dll, but I don't see > what script it's executing. Outlook2000\addin.py is the 'entry-point' - although the entry-point is actually the COM classes in that file, hence there is no __main__ block. You will notice all the initialization done in the mainline (eg, the code-block I mentioned yesterday) which would be a good place to start. Sadly, crashers like this can be hard to pin down without a debugger and debug versions of Python installed... Mark _______________________________________________ SpamBayes@python.org http://mail.python.org/mailman/listinfo/spambayes Info/Unsubscribe: http://mail.python.org/mailman/listinfo/spambayes Check the FAQ before asking: http://spambayes.sf.net/faq.html _______________________________________________ SpamBayes@python.org http://mail.python.org/mailman/listinfo/spambayes Info/Unsubscribe: http://mail.python.org/mailman/listinfo/spambayes Check the FAQ before asking: http://spambayes.sf.net/faq.html
