Re: [Pyobjc-dev] Seeing a traceback

[Anders H. <bo...@ki...>]

I agree this is pretty annoying and I think a pretty bad default
behavior. A workaround that I used recently is you make a try/except
block around all the code in the method you are interested in (in this
case I guess applicationDidFinishLaunching_ or similar) and do:

import traceback
traceback.print_exc()

Best Regards,
Anders Hovmöller

PS. Funnily enough I copied that code from a program I am writing
called "waker", are you also writing some alarm clock system? Send me
an email in that case, it'd be fun to discuss different approaches :P

On Sat, Dec 5, 2009 at 12:37 AM, Saptarshi Guha
<sap...@gm...> wrote:
> Hello,
> When running my PyObjc app, I get some errors, but no traceback
>
> e.g in the console (XCode's)
>
> 2009-12-04 18:32:31.643 Awake[5689:10b] Awake did finish launching.
> 2009-12-04 18:32:31.644 Awake[5689:10b] Using the following
> wakeupfile:/Users/yanger/.wakeuprc
> 2009-12-04 18:32:31.653 Awake[5689:10b] <type 'exceptions.TypeError'>:
> 'NoneType' object is not iterable
>
> But I'd like to see the traceback for the last line. Is there  a way
> for me to view it?
> Regards
> Saptarshi
> PYObjc on leopard 10.5.8 (Macbook)
>
> ------------------------------------------------------------------------------
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing.
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>