[New-bugs-announce] [issue17799] settrace docs are wrong about "c_call" events

Ned Batchelder report at bugs.python.org
Sat Apr 20 05:36:20 CEST 2013

New submission from Ned Batchelder:

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.

assignee: docs at python
components: Documentation
messages: 187406
nosy: docs at python, nedbat
priority: low
severity: normal
status: open
title: settrace docs are wrong about "c_call" events
versions: Python 2.7, Python 3.3

Python tracker <report at bugs.python.org>

More information about the New-bugs-announce mailing list