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 roger.serwy
Recipients loewis, roger.serwy, serhiy.storchaka, terry.reedy
Date 2012-07-13.19:19:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1342207197.29.0.133434448777.issue15335@psf.upfronthosting.co.za>
In-reply-to
Content
> I suggest to add a decorator @Debugger.internal for all methods that the debugger should not step into. It should set a function attribute that the debugger then checks for.


The decorator idea may work. I'll need to see how to make it work with the existing debugging code.


> OTOH, I fail to see the problem. Stepping through the standard library may be useful, and if you don't want to do that, you can choose to step over still.


I'm not sure why stepping through an IDE's internals is desirable when debugging one's own program. As it stands, the _RPCFile patch represents an unintended behavior change to the debugger. That needs to be either corrected or documented.
History
Date User Action Args
2012-07-13 19:19:57roger.serwysetrecipients: + roger.serwy, loewis, terry.reedy, serhiy.storchaka
2012-07-13 19:19:57roger.serwysetmessageid: <1342207197.29.0.133434448777.issue15335@psf.upfronthosting.co.za>
2012-07-13 19:19:56roger.serwylinkissue15335 messages
2012-07-13 19:19:56roger.serwycreate