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 belopolsky
Recipients belopolsky, eli.bendersky, terry.reedy
Date 2010-07-26.17:36:07
SpamBayes Score 7.009017e-05
Marked as misclassified No
Message-id <AANLkTi=MnH2o8m8bbLdXAEjnHP7hp8+0s=zc4-32hu8s@mail.gmail.com>
In-reply-to <1280119765.6.0.405609709685.issue9315@psf.upfronthosting.co.za>
Content
On Mon, Jul 26, 2010 at 12:49 AM, Eli Bendersky <report@bugs.python.org> wrote:
..
> This raises a question: should method names of classes come after the class names when appearing
> in a trace? Intuitively yes, but I want to investigate some more, probably by adding a couple more test
> cases where the traced functions are methods of objects rather than plain functions.
>

I want to agree, but finding the class name of the method may not be
trivial in 3.x because we don't have unbound methods anymore.   Please
bring this up on python-dev.
History
Date User Action Args
2010-07-26 17:36:09belopolskysetrecipients: + belopolsky, terry.reedy, eli.bendersky
2010-07-26 17:36:08belopolskylinkissue9315 messages
2010-07-26 17:36:07belopolskycreate