Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
CPython only very recently started keeping a reference on frames to function objects internally, and that reference isn't exposed from inside Python. There's an old PEP that would have defined a _...
Answer
#1: Initial revision
CPython only very recently started keeping a reference on frames to function objects internally, and that reference isn't exposed from inside Python. There's [an old PEP](https://peps.python.org/pep-3130/) that would have defined a `__function__` local, which, combined with the `f_locals` field on frame objects, probably would have done what you needed. Unfortunately, the PEP was rejected, and I don't see any current activity in the direction of exposing a frame's function object via any other means. For limited cases, if you make various assumptions about what variables are named or what kind of functions get decorated, you can possibly bodge in something that will work some of the time by inspecting a parent frame's `f_locals` and `f_globals` and looking for a function object that matches what the current frame is doing. But a technique suitable for a general-purpose debugger is probably impossible. You probably already know, but the `Pdb` class accepts a `skip` argument which allows the debugger to skip code in modules that match wildcards. Depending on which decorators you need to skip and how you structure your code, using this feature might be better for you than attempting to subclass `Pdb`.