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 eric.araujo, ezio.melotti, terry.reedy
Date 2011-09-12.16:46:13
SpamBayes Score 2.51589e-07
Marked as misclassified No
Message-id <1315845974.18.0.361355480391.issue12913@psf.upfronthosting.co.za>
In-reply-to
Content
Binary search with print is done manually. If error not obvious from quick read, in a 20 line function, add print around line 10. If ok there, look down and add print later in function. If not, look up and add print earlier in function. This is not exact at all, but quick reruns (F5 with IDLE) mean no need to load up entire function with prints (that will have to be removed again) all at once (as might do with compiled C 20 years ago). Same idea as binary search through revisions to find buildbot breaker. I am sure you know this, even if not by terms I used.
History
Date User Action Args
2011-09-12 16:46:14terry.reedysetrecipients: + terry.reedy, ezio.melotti, eric.araujo
2011-09-12 16:46:14terry.reedysetmessageid: <1315845974.18.0.361355480391.issue12913@psf.upfronthosting.co.za>
2011-09-12 16:46:13terry.reedylinkissue12913 messages
2011-09-12 16:46:13terry.reedycreate