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 gwk
Recipients ammar2, gwk, vstinner, xdegaye
Date 2017-02-01.22:55:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Xavier, this is a misunderstanding; sorry for not being more clear. When I said "remove the `else`", I was proposing this:

+ if (tstate->inst_tracing) {
+   result = call_trace(func, obj, tstate, frame, PyTrace_INSTRUCTION, Py_None);
+ }

Line-oriented tracers/debuggers would not have set trace_instructions, so they would not receive any 'instruction' events, and should not suffer.

The motivation for this suggestion was that for tracers that *are* interested in instructions, it *might* be simpler to get two calls, one of 'line', and one of 'instruction'. Maybe it's a bad idea though.
Date User Action Args
2017-02-01 22:55:21gwksetrecipients: + gwk, vstinner, xdegaye, ammar2
2017-02-01 22:55:21gwksetmessageid: <>
2017-02-01 22:55:21gwklinkissue29400 messages
2017-02-01 22:55:21gwkcreate