exceptions, internals (introspection? )

[ej]

I'm trying to figure out how to get at some of the internal interpreter
state for exception handlers and debug statements in general.
I just read through Section 8 of the Python Tutorial. I see how to catch an
exception, and specify an optional argument to get ahold of the exception
itself. For example:

try:
{}['foo']
except Exception, x:
print "class of x =", x.__class__
print "type(x) =", type(x)
print "dir(x) =", dir(x)
If you don't handle an exception, the interpreter will quit and print a
stack trace. What I'm not seeing is how to handle the exception, but still
get the stack trace as a string so I could dump it to a log file or email it
or something.

I have often wondered how to get at other internals, such as the name of
the current function, file, line number I am in? The arguments to the
current function, etc. I browsed through the table of contents of both the
Library Reference & Language Reference. I see section 18. Python Language
Services. In browsing through that, I'm thinking "Oh man... this is way
more than I need - there's got to be an easier way." Nothing else is
jumping out at me. Can someone point me to some documentation on this
subject and/or provide some examples?

Thanks, :)
-ej

[Paul Rubin]

"ej" <ej at wellkeeper com> writes:

I have often wondered how to get at other internals, such as the name of
the current function, file, line number I am in? The arguments to the
current function, etc.

It's messy. Look at sys.exc_info() and go from there.

[Fredrik Lundh]

"ej" <"ej atwellkeepercom "@bag.python.or g> wrote

try:
{}['foo']
except Exception, x:
print "class of x =", x.__class__
print "type(x) =", type(x)
print "dir(x) =", dir(x)

If you don't handle an exception, the interpreter will quit and print a
stack trace. What I'm not seeing is how to handle the exception, but still
get the stack trace as a string so I could dump it to a log file or email it
or something.

the second example on this page shows you how to do that:

http://effbot.org/librarybook/traceback

</F>

[Paul McNett]

ej wrote:

I have often wondered how to get at other internals, such as the name of
the current function, file, line number I am in? The arguments to the
current function, etc.

Others have given you information on how to get at the stack trace. But
regarding getting at some of the other internals you are talking about:

import inspect
help(inspect)

Back to exceptions, you can also provide your own global exception handler by
overriding sys.excepthook (drop in your own function).

--
Paul McNett
http://paulmcnett.com
http://dabodev.com

[ej]

"Paul Rubin" <http://ph****@NOSPAM.i nvalid> wrote in message
news:7x******** ****@ruckus.bro uhaha.com...

It's messy. Look at sys.exc_info() and go from there.

Yeah, I think I am starting to see what you mean...
#! /usr/local/bin/python

import sys

try:
{}['foo']
except Exception, x:
print "class of x =", x.__class__
print "type(x) =", type(x)
print "dir(x) =", dir(x)

print
(type_, value_, traceback_) = sys.exc_info()
print "type_ =", type_
print "value_ =", value_
print "traceback_ =", traceback_
for key in dir(traceback_) :
print "traceback_ .%s =" % key, eval("traceback _.%s" % key)

print "dir(frame) = ", dir(traceback_. tb_frame)
ej@sand:~/src/python/exceptions> foo
class of x = exceptions.KeyE rror
type(x) = <type 'instance'>
dir(x) = ['__doc__', '__getitem__', '__init__', '__module__', '__str__',
'args']

type_ = exceptions.KeyE rror
value_ = 'foo'
traceback_ = <traceback object at 0x402e2e14>
traceback_.tb_f rame = <frame object at 0x8177b3c>
traceback_.tb_l asti = 18
traceback_.tb_l ineno = 6
traceback_.tb_n ext = None
dir(frame) = ['__class__', '__delattr__', '__doc__', '__getattribute __',
'__hash__', '__init__', '__new__', '__reduce__', '__reduce_ex__' ,
'__repr__', '__setattr__', '__str__', 'f_back', 'f_builtins', 'f_code',
'f_exc_tracebac k', 'f_exc_type', 'f_exc_value', 'f_globals', 'f_lasti',
'f_lineno', 'f_locals', 'f_restricted', 'f_trace']

But at least that is something to go on. Thanks for your reply!

-ej

[ej]

"Fredrik Lundh" <fr*****@python ware.com> wrote in message
news:ma******** *************** *************** @python.org...

the second example on this page shows you how to do that:

http://effbot.org/librarybook/traceback

I am looking at it. Thanks for your prompt reply, Mr. Lundh! :)

-ej

[Paul Rubin]

"ej" <ej at wellkeeper com> writes:

for key in dir(traceback_) :
print "traceback_ .%s =" % key, eval("traceback _.%s" % key)
Don't use eval for this. Use getattr(traceba ck_, key).
traceback_.tb_f rame = <frame object at 0x8177b3c>
traceback_.tb_l asti = 18
traceback_.tb_l ineno = 6
traceback_.tb_n ext = None

Yeah. As /F mentioned, there's also a traceback module that parses
this stuff out for you.

[Fernando Perez]

ej wrote:

I have often wondered how to get at other internals, such as the name of
the current function, file, line number I am in? The arguments to the
current function, etc. I browsed through the table of contents of both the
Library Reference & Language Reference. I see section 18. Python Language
Services. In browsing through that, I'm thinking "Oh man... this is way
more than I need - there's got to be an easier way." Nothing else is
jumping out at me. Can someone point me to some documentation on this
subject and/or provide some examples?

Poke around IPython, which implements a pretty massive amount of functionality
in this direction. In particular, you want to read OInspect.py and ultraTB.py.

Cheers,

f