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 | amaury.forgeotdarc, belopolsky, nedbat, rhettinger |
| Date | 2008年03月29日.20:58:19 |
| SpamBayes Score | 0.020756554 |
| Marked as misclassified | No |
| Message-id | <1206824300.2.0.424117647453.issue2506@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
This has basically almost never been a problem in the real world. No need to complicate the world further by adding yet another option and the accompanying implementation-specific knowledge of why you would ever want to use it. Also, when the peepholer is moved (after the AST is created, but before the opcodes), then little oddities like this will go away. Recommend closing as "won't fix". |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月29日 20:58:20 | rhettinger | set | spambayes_score: 0.0207566 -> 0.020756554 recipients: + rhettinger, amaury.forgeotdarc, belopolsky, nedbat |
| 2008年03月29日 20:58:20 | rhettinger | set | spambayes_score: 0.0207566 -> 0.0207566 messageid: <1206824300.2.0.424117647453.issue2506@psf.upfronthosting.co.za> |
| 2008年03月29日 20:58:19 | rhettinger | link | issue2506 messages |
| 2008年03月29日 20:58:19 | rhettinger | create | |