Created on 2010-07-12 22:28 by rocky, last changed 2010-10-17 11:06 by georg.brandl. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg110145 - (view) | Author: rocky bernstein (rocky) | Date: 2010-07-12 22:27 | |
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. |
|||
| msg111388 - (view) | Author: Terry J. Reedy (terry.reedy) *  |
Date: 2010-07-23 21:27 | |
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 |
|||
| msg118937 - (view) | Author: Georg Brandl (georg.brandl) * |
Date: 2010-10-17 11:06 | |
Documented in r85636. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-10-17 11:06:22 | georg.brandl | set | status: open -> closed nosy: + georg.brandl messages: + msg118937 resolution: fixed |
| 2010-07-23 21:27:00 | terry.reedy | set | versions:
- Python 2.5, Python 3.3 nosy: + terry.reedy messages: + msg111388 keywords: + easy stage: needs patch |
| 2010-07-12 22:28:00 | rocky | create | |