The inspect module provides several useful functions to help get information about live objects such as modules, classes, methods, functions, tracebacks, frame objects, and code objects. For example, it can help you examine the contents of a class, retrieve the source code of a method, extract and format the argument list for a function, or get all the information you need to display a detailed traceback.
There are four main kinds of services provided by this module: type checking, getting source code, inspecting classes and functions, and examining the interpreter stack.
The getmembers() function retrieves the members of an object such as a class or module. The sixteen functions whose names begin with “is” are mainly provided as convenient choices for the second argument to getmembers(). They also help you determine when you can expect to find the following special attributes:
|__file__||filename (missing for built-in modules)|
|__module__||name of module in which this class was defined|
|__name__||name with which this method was defined|
|__func__||function object containing implementation of method|
|__self__||instance to which this method is bound, or None|
|__name__||name with which this function was defined|
|__code__||code object containing compiled function bytecode|
|__defaults__||tuple of any default values for arguments|
|__globals__||global namespace in which this function was defined|
|traceback||tb_frame||frame object at this level|
|tb_lasti||index of last attempted instruction in bytecode|
|tb_lineno||current line number in Python source code|
|tb_next||next inner traceback object (called by this level)|
|frame||f_back||next outer frame object (this frame’s caller)|
|f_builtins||built-in namespace seen by this frame|
|f_code||code object being executed in this frame|
|f_globals||global namespace seen by this frame|
|f_lasti||index of last attempted instruction in bytecode|
|f_lineno||current line number in Python source code|
|f_locals||local namespace seen by this frame|
|f_restricted||0 or 1 if frame is in restricted execution mode|
|f_trace||tracing function for this frame, or None|
|code||co_argcount||number of arguments (not including * or ** args)|
|co_code||string of raw compiled bytecode|
|co_consts||tuple of constants used in the bytecode|
|co_filename||name of file in which this code object was created|
|co_firstlineno||number of first line in Python source code|
|co_flags||bitmap: 1=optimized | 2=newlocals | 4=*arg | 8=**arg|
|co_lnotab||encoded mapping of line numbers to bytecode indices|
|co_name||name with which this code object was defined|
|co_names||tuple of names of local variables|
|co_nlocals||number of local variables|
|co_stacksize||virtual machine stack space required|
|co_varnames||tuple of names of arguments and local variables|
|__name__||original name of this function or method|
|__self__||instance to which a method is bound, or None|
Return all the members of an object in a list of (name, value) pairs sorted by name. If the optional predicate argument is supplied, only members for which the predicate returns a true value are included.
This, for example, is true of int.__add__. An object passing this test has a __get__ attribute but not a __set__ attribute, but beyond that the set of attributes varies. __name__ is usually sensible, and __doc__ often is.
Methods implemented via descriptors that also pass one of the other tests return false from the ismethoddescriptor() test, simply because the other tests promise more – you can, e.g., count on having the __func__ attribute (etc) when an object passes ismethod().
Return true if the object is a data descriptor.
Data descriptors have both a __get__ and a __set__ attribute. Examples are properties (defined in Python), getsets, and members. The latter two are defined in C and there are more specific tests available for those types, which is robust across Python implementations. Typically, data descriptors will also have __name__ and __doc__ attributes (properties, getsets, and members have both of these attributes), but this is not guaranteed.
Return true if the object is a getset descriptor.
CPython implementation detail: getsets are attributes defined in extension modules via PyGetSetDef structures. For Python implementations without such types, this method will always return False.
Get the names and default values of a function’s arguments. A named tuple ArgSpec(args, varargs, keywords, defaults) is returned. args is a list of the argument names. varargs and varkw are the names of the * and ** arguments or None. defaults is a tuple of default argument values or None if there are no default arguments; if this tuple has n elements, they correspond to the last n elements listed in args.
Deprecated since version 3.0: Use getfullargspec() instead, which provides information about keyword-only arguments and annotations.
Get the names and default values of a function’s arguments. A named tuple is returned:
FullArgSpec(args, varargs, varkw, defaults, kwonlyargs, kwonlydefaults, annotations)
args is a list of the argument names. varargs and varkw are the names of the * and ** arguments or None. defaults is an n-tuple of the default values of the last n arguments. kwonlyargs is a list of keyword-only argument names. kwonlydefaults is a dictionary mapping names from kwonlyargs to defaults. annotations is a dictionary mapping argument names to annotations.
The first four items in the tuple correspond to getargspec().
When the following functions return “frame records,” each record is a tuple of six items: the frame object, the filename, the line number of the current line, the function name, a list of lines of context from the source code, and the index of the current line within that list.
Keeping references to frame objects, as found in the first element of the frame records these functions return, can cause your program to create reference cycles. Once a reference cycle has been created, the lifespan of all objects which can be accessed from the objects which form the cycle can become much longer even if Python’s optional cycle detector is enabled. If such cycles must be created, it is important to ensure they are explicitly broken to avoid the delayed destruction of objects and increased memory consumption which occurs.
Though the cycle detector will catch these, destruction of the frames (and local variables) can be made deterministic by removing the cycle in a finally clause. This is also important if the cycle detector was disabled when Python was compiled or using gc.disable(). For example:
def handle_stackframe_without_leak(): frame = inspect.currentframe() try: # do something with the frame finally: del frame
The optional context argument supported by most of these functions specifies the number of lines of context to return, which are centered around the current line.
Return the frame object for the caller’s stack frame.
CPython implementation detail: This function relies on Python stack frame support in the interpreter, which isn’t guaranteed to exist in all implementations of Python. If running in an implementation without Python stack frame support this function returns None.