➜

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 rhettinger
Recipients doublep, rhettinger
Date 2008-05-31.04:59:25
SpamBayes Score 0.03573102
Marked as misclassified No
Message-id <1212209971.09.0.433130500559.issue1764986@psf.upfronthosting.co.za>
In-reply-to
Content 
Not too excited about this.  It adds to compilation time but doesn't 
save any runtime.  It's not at all common for production code to have 
unreachable code at RAISE_VARARGS or BREAK_LOOP, so I see no reason to 
complexify to the peepholer to handle this case.
History
Date User Action Args
2008-05-31 04:59:31rhettingersetspambayes_score: 0.035731 -> 0.03573102
recipients: + rhettinger, doublep
2008-05-31 04:59:31rhettingersetspambayes_score: 0.035731 -> 0.035731
messageid: <1212209971.09.0.433130500559.issue1764986@psf.upfronthosting.co.za>
2008-05-31 04:59:27rhettingerlinkissue1764986 messages
2008-05-31 04:59:26rhettingercreate