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 serhiy.storchaka
Recipients Mark.Shannon, nedbat, serhiy.storchaka
Date 2018-09-16.14:39:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Humm, the optimization is not related here. Even if it is not involved (replace 17 with []), the line 4 is reported twice, because RETURN_VALUE is executed after CALL_FINALLY.

  4          10 BUILD_LIST               0
             12 POP_BLOCK
             14 CALL_FINALLY             2 (to 18)
             16 RETURN_VALUE

In 3.7 RETURN_VALUE was the opcode executed at line 4. The stack of blocks was unwinded at interpreted loop implicitly when execute RETURN_VALUE. But in 3.8 calling the finally code is explicit.
Date User Action Args
2018-09-16 14:39:03serhiy.storchakasetrecipients: + serhiy.storchaka, nedbat, Mark.Shannon
2018-09-16 14:39:02serhiy.storchakasetmessageid: <>
2018-09-16 14:39:02serhiy.storchakalinkissue34705 messages
2018-09-16 14:39:02serhiy.storchakacreate