➜

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 ncoghlan
Recipients Demur Rumed, Mark.Shannon, benjamin.peterson, christian.heimes, mark.dickinson, nascheme, ncoghlan, pitrou, rhettinger, serhiy.storchaka, trent
Date 2017-12-30.01:03:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7fedPwhCQ3m-UhwARXdutvcGxOK5R7tOP0svBuNH+oRgw@mail.gmail.com>
In-reply-to <2476627.uTek7ZXOIG@saraksh>
Content 
Another point in favour of the JSR approach is that it should make it
easier for tools like coverage.py to continue mapping opcode coverage to
line coverage.

I also like Serhiy's proposed strategy of separating the initial
introduction of the compiler based exception handling from the subsequent
simplification of the exception handling opcodes.
History
Date User Action Args
2017-12-30 01:03:30ncoghlansetrecipients: + ncoghlan, nascheme, rhettinger, mark.dickinson, pitrou, christian.heimes, benjamin.peterson, trent, Mark.Shannon, serhiy.storchaka, Demur Rumed
2017-12-30 01:03:30ncoghlanlinkissue17611 messages
2017-12-30 01:03:28ncoghlancreate