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 xdegaye
Date 2012-12-12.21:48:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1355348931.03.0.35406235463.issue16672@psf.upfronthosting.co.za>
In-reply-to
Content
> When f_trace is NULL, only PyTrace_CALL tracing events trigger the invocation
> of the trace function (see trace_trampoline).

This may be confusing. I meant that when f_trace is NULL, PyTrace_LINE,
PyTrace_RETURN and PyTrace_EXCEPTION are not traced.
History
Date User Action Args
2012-12-12 21:48:51xdegayesetrecipients: + xdegaye
2012-12-12 21:48:51xdegayesetmessageid: <1355348931.03.0.35406235463.issue16672@psf.upfronthosting.co.za>
2012-12-12 21:48:51xdegayelinkissue16672 messages
2012-12-12 21:48:50xdegayecreate