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-23.13:49:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1358948944.44.0.422142287475.issue16672@psf.upfronthosting.co.za>
In-reply-to
Content
It is not possible to improve the performances of the trace function set with
sys.settrace without breaking backward compatibility for PyEval_SetTrace or
without introducing a new PyEval_xxx of some sort.

Yes, I suggest to revert this patch.
History
Date User Action Args
2013-01-23 13:49:04xdegayesetrecipients: + xdegaye, georg.brandl, jcea, belopolsky, pitrou, benjamin.peterson, asvetlov, python-dev
2013-01-23 13:49:04xdegayesetmessageid: <1358948944.44.0.422142287475.issue16672@psf.upfronthosting.co.za>
2013-01-23 13:49:04xdegayelinkissue16672 messages
2013-01-23 13:49:04xdegayecreate