Message 165815 - Python tracker

➜

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	ltaylor934, roger.serwy, terry.reedy
Date	2012-07-18.22:16:26
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1342649789.9.0.158166833073.issue14105@psf.upfronthosting.co.za>
In-reply-to

Content
The ColorDelegator is responsible for providing the coloring for the BREAK tag which is used to mark breakpoints. When recoloring, the BREAK tag may be removed (find self.tag_remove in recolorize_main). This is precisely why the breakpoints disappear. On 2.7, you can use Control-/ to toggle the ColorDelegator. Doing so eliminates the behavior you describe. On 3.x, Control-/ is broken due to two ColorDelegators being loaded. See issue13495. A possible solution would be to separate the BREAK tags from the color delegator since these tags ought to be part of the debugging code only.

The ColorDelegator is responsible for providing the coloring for the BREAK tag which is used to mark breakpoints. When recoloring, the BREAK tag may be removed (find self.tag_remove in recolorize_main). This is precisely why the breakpoints disappear.

On 2.7, you can use Control-/ to toggle the ColorDelegator. Doing so eliminates the behavior you describe. On 3.x, Control-/ is broken due to two ColorDelegators being loaded. See issue13495.

A possible solution would be to separate the BREAK tags from the color delegator since these tags ought to be part of the debugging code only.

History
Date	User	Action	Args
2012-07-18 22:16:30	roger.serwy	set	recipients: + roger.serwy, terry.reedy, ltaylor934
2012-07-18 22:16:29	roger.serwy	set	messageid: <1342649789.9.0.158166833073.issue14105@psf.upfronthosting.co.za>
2012-07-18 22:16:28	roger.serwy	link	issue14105 messages
2012-07-18 22:16:26	roger.serwy	create