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 belopolsky, rhettinger
Date 2008-06-12.22:08:48
SpamBayes Score 0.010381169
Marked as misclassified No
Message-id <1213308530.8.0.844046839982.issue2493@psf.upfronthosting.co.za>
In-reply-to
Content
The issue with unused constants is an artifact of the peepholer running 
after the bytecode generation phase.  When constant folding was 
written, I intentionally left-out a step to remove unused constants 
because of the code complexity, the fragility of the process, because 
the benefits were inconsequential, and because it added to compilation 
time.  

It would be better to wait for the AST optimizer to replace the 
peepholer.  AST optimizations are upstream from bytecode generation, so 
the unused constant issue simply disappears.
History
Date User Action Args
2008-06-12 22:08:51rhettingersetspambayes_score: 0.0103812 -> 0.010381169
recipients: + rhettinger, belopolsky
2008-06-12 22:08:50rhettingersetspambayes_score: 0.0103812 -> 0.0103812
messageid: <1213308530.8.0.844046839982.issue2493@psf.upfronthosting.co.za>
2008-06-12 22:08:50rhettingerlinkissue2493 messages
2008-06-12 22:08:49rhettingercreate