[Python-ideas] Python-ideas Digest, Vol 90, Issue 30

[Ned Batchelder]

On 5/21/14 6:50 PM, Greg Ewing wrote:
> Raymond Hettinger wrote:
>> * I sympathize with "there is an irritating dimple in coverage.py"
>> but that hasn't actually impaired its usability beyond creating a
>> curiosity.
>
> Another way to address this would be to make coverage.py
> smart enough to understand when a source line has been
> optimised away and always report it as executed.
>
Do you have any ideas about that could possibly work? 
Reverse-engineering optimized code is difficult if not impossible. I'm 
open to concrete ideas though.

--Ned.