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 eli.bendersky
Recipients belopolsky, eli.bendersky, terry.reedy
Date 2010-07-26.04:49:20
SpamBayes Score 0.0005752554
Marked as misclassified No
Message-id <1280119765.6.0.405609709685.issue9315@psf.upfronthosting.co.za>
In-reply-to
Content
The test failure of the py3k ports boils down to this: the 'runfunc' method of 'Trace' appears as a caller to '_traced_func_importing_caller'. In 2.7 it appears as 'Trace.runfunc', in py3k as just 'runfunc'.

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 hope to get to it later today. If not, later this week. In any case, I will address both this issue and your other comments and will submit a new patch.

Thanks for the quick review.
History
Date User Action Args
2010-07-26 04:49:26eli.benderskysetrecipients: + eli.bendersky, terry.reedy, belopolsky
2010-07-26 04:49:25eli.benderskysetmessageid: <1280119765.6.0.405609709685.issue9315@psf.upfronthosting.co.za>
2010-07-26 04:49:23eli.benderskylinkissue9315 messages
2010-07-26 04:49:20eli.benderskycreate