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 ncoghlan
Recipients gregory.p.smith, ncoghlan, nedbat, njs, serhiy.storchaka
Date 2017-09-05.21:05:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1504645546.09.0.216928831769.issue31344@psf.upfronthosting.co.za>
In-reply-to
Content
Steve's also requested the ability to *turn off* line debugging, and I'm thinking it may make sense to allow all four configurations:

* both line and opcode events disabled
* only getting one or the other
* getting both kinds of event

Opcode events would definitely be off by default, and if you do turn them on, then you'd be in a situation similar to importing ctypes: the interpreter is no longer guaranteed to work correctly. (Although unlike ctypes, you shouldn't get segfaults because of it)
History
Date User Action Args
2017-09-05 21:05:46ncoghlansetrecipients: + ncoghlan, gregory.p.smith, nedbat, njs, serhiy.storchaka
2017-09-05 21:05:46ncoghlansetmessageid: <1504645546.09.0.216928831769.issue31344@psf.upfronthosting.co.za>
2017-09-05 21:05:46ncoghlanlinkissue31344 messages
2017-09-05 21:05:46ncoghlancreate