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 terry.reedy
Recipients kbk, markroseman, roger.serwy, terry.reedy
Date 2015-09-20.05:56:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1442728561.64.0.302474196031.issue25146@psf.upfronthosting.co.za>
In-reply-to
Content
I had a wild idea, possible a result of too much ignorance.  Run the main debugger in the user process, with a separate root and event loop.  Add to the communication protocol options to send a list of breakpoints and modules to be traced into and to send (module, lineno) pairs back, for highlighting in the editor.

I am willing for a revised debugger to not work with -n.  We want that to go away anyway.  Roger Serwy sent some of us a prototype pipe implementation a year ago when I was busy with GSOC, and I did not pursue it yet.
History
Date User Action Args
2015-09-20 05:56:01terry.reedysetrecipients: + terry.reedy, kbk, roger.serwy, markroseman
2015-09-20 05:56:01terry.reedysetmessageid: <1442728561.64.0.302474196031.issue25146@psf.upfronthosting.co.za>
2015-09-20 05:56:01terry.reedylinkissue25146 messages
2015-09-20 05:56:00terry.reedycreate