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 xdegaye
Recipients asvetlov, belopolsky, benjamin.peterson, georg.brandl, jcea, pitrou, python-dev, xdegaye
Date 2013-01-22.16:06:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
One may argue that this is not only a performances patch and that it
fixes the wasting of cpu resources when tracing is on. Wasting cpu
resources is a bug. Anyway, this is fine with me to close this minor
issue on 2.7.

The test_hotshot test is ok on my linux box and with the patch applied
on 2.7 head. Just curious to know what the problem is.

And thanks for applying the patch to 3.4.
Date User Action Args
2013-01-22 16:06:36xdegayesetrecipients: + xdegaye, georg.brandl, jcea, belopolsky, pitrou, benjamin.peterson, asvetlov, python-dev
2013-01-22 16:06:36xdegayesetmessageid: <>
2013-01-22 16:06:36xdegayelinkissue16672 messages
2013-01-22 16:06:36xdegayecreate