Author eltoder
Recipients Jeremy.Hylton, Trundle, alex, benjamin.peterson, brett.cannon, daniel.urban, dmalcolm, eltoder, eric.snow, georg.brandl, gregory.p.smith, jcon, mark.dickinson, meador.inge, nadeem.vawda, ncoghlan, pitrou, rhettinger, santoso.wijaya, techtonik, terry.reedy, vstinner
Date 2012-09-06.01:20:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1346894424.55.0.169630324232.issue11549@psf.upfronthosting.co.za>
In-reply-to
Content
> Method calls on literals are always fair game, though (e.g. you could optimise "a b c".split())
What about optimizations that do not change behavior, except for different error messages? E.g. we can change
y = [1,2][x]
to
y = (1,2)[x]
where the tuple is constant and is stored in co_consts. This will, however, produce a different text in the exception when x is not 0 or 1. The type of exception is going to be the same.
History
Date User Action Args
2012-09-06 01:20:24eltodersetrecipients: + eltoder, brett.cannon, georg.brandl, rhettinger, terry.reedy, gregory.p.smith, mark.dickinson, ncoghlan, pitrou, vstinner, techtonik, nadeem.vawda, benjamin.peterson, alex, Trundle, dmalcolm, meador.inge, daniel.urban, Jeremy.Hylton, santoso.wijaya, eric.snow, jcon
2012-09-06 01:20:24eltodersetmessageid: <1346894424.55.0.169630324232.issue11549@psf.upfronthosting.co.za>
2012-09-06 01:20:24eltoderlinkissue11549 messages
2012-09-06 01:20:23eltodercreate