This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients belopolsky, pitrou, rhettinger
Date 2011-04-11.21:21:02
SpamBayes Score 2.4688496e-05
Marked as misclassified No
Message-id <1302556860.3783.3.camel@localhost.localdomain>
In-reply-to <1302556390.79.0.361647840169.issue11822@psf.upfronthosting.co.za>
Content
> 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.
History
Date User Action Args
2011-04-11 21:21:03pitrousetrecipients: + pitrou, rhettinger, belopolsky
2011-04-11 21:21:03pitroulinkissue11822 messages
2011-04-11 21:21:02pitroucreate