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 xdegaye
Recipients ammar2, gwk, vstinner, xdegaye
Date 2017-02-01.22:28:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1485988080.19.0.715381234876.issue29400@psf.upfronthosting.co.za>
In-reply-to
Content
> About performances: it's fine to add anything to maybe_call_line_trace(), it cannot impact performances when tracing is not used.

I do not agree, Python debuggers are already really really slow. They should not have to process 'instruction' trace events as this would happen if George does "Remove the `else` to always trace with PyTrace_INSTRUCTION, rather than as an alternate to PyTrace_LINE as it does now".
I understand that this was a suggestion :)
History
Date User Action Args
2017-02-01 22:28:00xdegayesetrecipients: + xdegaye, vstinner, gwk, ammar2
2017-02-01 22:28:00xdegayesetmessageid: <1485988080.19.0.715381234876.issue29400@psf.upfronthosting.co.za>
2017-02-01 22:28:00xdegayelinkissue29400 messages
2017-02-01 22:28:00xdegayecreate