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 | ajaksu2, amaury.forgeotdarc, belopolsky, nedbat, rhettinger |
| Date | 2008年03月31日.01:59:37 |
| SpamBayes Score | 0.014263178 |
| Marked as misclassified | No |
| Message-id | <1206928778.56.0.064655280715.issue2506@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Marking this one as closed. Also, rejecting the various ways to disable peephole optimization. This was discussed with Guido long ago and the decision essentially recognized that for most practical purposes the output of the peepholer is the generated code and no good would come from exposing upstream intermediate steps. Since then, I believe Neal got Guido's approval for either the -O or - OO option to generate new optimizations that potentially change semantics. In that situation, there is a worthwhile reason for the enable/disable option. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月31日 01:59:38 | rhettinger | set | spambayes_score: 0.0142632 -> 0.014263178 recipients: + rhettinger, amaury.forgeotdarc, belopolsky, ajaksu2, nedbat |
| 2008年03月31日 01:59:38 | rhettinger | set | spambayes_score: 0.0142632 -> 0.0142632 messageid: <1206928778.56.0.064655280715.issue2506@psf.upfronthosting.co.za> |
| 2008年03月31日 01:59:38 | rhettinger | link | issue2506 messages |
| 2008年03月31日 01:59:37 | rhettinger | create | |