classification
Title: settrace docs are wrong about "c_call" events
Type: behavior Stage: patch review
Components: Documentation Versions: Python 3.5, Python 3.4, Python 2.7
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, ionelmc, nedbat, raylu, xiang.zhang
Priority: low Keywords: patch

Created on 2013-04-20 03:36 by nedbat, last changed 2018-01-11 09:12 by BreamoreBoy.

Pull Requests
URL Status Linked Edit
PR 4056 open pablogsal, 2017-10-20 09:04
Messages (3)
msg187406 - (view) Author: Ned Batchelder (nedbat) * Date: 2013-04-20 03:36
Looking into this Stack Overflow question:  http://stackoverflow.com/questions/16115027/pythons-sys-settrace-wont-create-c-call-events

Reading the code in c_eval.c and friends, it looks like "c_call" events are never passed to the trace function, only to the profile function.  The docs are wrong and should be fixed.

The setprofile docs simply point to settrace for details, so the text needs to accommodate both functions' needs.
msg228143 - (view) Author: Mark Lawrence (BreamoreBoy) * Date: 2014-10-02 00:21
@Ned can you provide a patch for this?
msg309797 - (view) Author: Xiang Zhang (xiang.zhang) * (Python committer) Date: 2018-01-11 09:10
Is there any reason not to respond to "c_call" events in trace function?
History
Date User Action Args
2018-01-11 09:12:45BreamoreBoysetnosy: - BreamoreBoy
2018-01-11 09:10:45xiang.zhangsetnosy: + xiang.zhang
messages: + msg309797
2017-10-20 09:04:12pablogsalsetkeywords: + patch
stage: patch review
pull_requests: + pull_request4025
2017-10-19 09:27:26raylusetnosy: + raylu
2015-03-18 21:35:47ionelmcsetnosy: + ionelmc
2014-10-02 00:21:22BreamoreBoysetversions: + Python 3.4, Python 3.5, - Python 3.3
nosy: + BreamoreBoy

messages: + msg228143

type: behavior
2013-04-20 03:36:20nedbatcreate