➜

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 benjamin.peterson
Recipients BTaskaya, Mark.Shannon, benjamin.peterson, nedbat, pablogsal, rhettinger, serhiy.storchaka
Date 2020-12-23.03:42:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1608694924.5.0.427484925268.issue42693@roundup.psfhosted.org>
In-reply-to
Content 
Maybe sys.settrace() is not ultimately the best tool for coverage reporting? If the bytecode compiler natively supported coverage instrumentation, source semantics would be easier to respect. A nice implementation could use Knuth & Stevenson "Optimal measurement of points for program frequency counts".
History
Date User Action Args
2020-12-23 03:42:04benjamin.petersonsetrecipients: + benjamin.peterson, rhettinger, nedbat, Mark.Shannon, serhiy.storchaka, pablogsal, BTaskaya
2020-12-23 03:42:04benjamin.petersonsetmessageid: <1608694924.5.0.427484925268.issue42693@roundup.psfhosted.org>
2020-12-23 03:42:04benjamin.petersonlinkissue42693 messages
2020-12-23 03:42:04benjamin.petersoncreate