[issue9237] Add sys.call_tracing to on-line sys module documentation
New submission from rocky bernstein <rocky@gnu.org>: sys.call_tracing doesn't appear in Python documents and I think it should. For a start, one could use the docstring from sysmodule.c: call_tracing(func, args) -> object Call func(*args), while tracing is enabled. The tracing state is saved, and restored afterwards. This is intended to be called from a debugger from a checkpoint, to recursively debug some other code. Thanks. ---------- assignee: docs@python components: Documentation messages: 110145 nosy: docs@python, rocky priority: normal severity: normal status: open title: Add sys.call_tracing to on-line sys module documentation type: feature request versions: Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3 _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue9237> _______________________________________
Terry J. Reedy <tjreedy@udel.edu> added the comment: I verified that in 3.1, sys.call_tracing exists but is undocumented. I also noticed that the sys doc entries are *almost* in alphabetical order. Out of place: subversion, dont_write_bytecode, api_version Reversed pairs (abbreviated) copyright clearxxx dllxxx disxxx getrefxx getrecxx ---------- keywords: +easy nosy: +tjreedy stage: -> needs patch versions: -Python 2.5, Python 3.3 _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue9237> _______________________________________
Georg Brandl <georg@python.org> added the comment: Documented in r85636. ---------- nosy: +georg.brandl resolution: -> fixed status: open -> closed _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue9237> _______________________________________
participants (3)
-
Georg Brandl
-
rocky bernstein
-
Terry J. Reedy