Antoine Pitrou <pit...@free.fr> added the comment: > If you disassemble a function, you typically want to see all the code > in that function.
That depends on the function. If you do event-driven programming (say, Twisted deferreds with addCallback()), you don't necessarily want to see the disassembly of the callbacks that are passed to the various framework functions. Also, if you do so recursively, it might become *very* unwieldy. So I don't think there's anything "typical" here. It depends on what you intend to focus on. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11822> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com