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 | nedbat |
|---|---|
| Recipients | amaury.forgeotdarc, belopolsky, nedbat, rhettinger |
| Date | 2008年03月29日.21:19:27 |
| SpamBayes Score | 0.023374157 |
| Marked as misclassified | No |
| Message-id | <1206825569.18.0.815058272969.issue2506@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I recognize that this is an unusual case, but it did come up in the real world. I found this while measuring test coverage, and the continue line was marked as not executed, when it was. I don't understand "when the peepholer is moved", so maybe you are right that this will no longer be an issue. But it seems to me to be endemic to code optimization to lose the one-to-one correspondence between source lines and ranges of bytecodes. And as the compiler becomes more complex and performs more optmizations, problems like this will likely increase, no? In any case, I'd like to know more about the changes planned for the AST and compiler... |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月29日 21:19:29 | nedbat | set | spambayes_score: 0.0233742 -> 0.023374157 recipients: + nedbat, rhettinger, amaury.forgeotdarc, belopolsky |
| 2008年03月29日 21:19:29 | nedbat | set | spambayes_score: 0.0233742 -> 0.0233742 messageid: <1206825569.18.0.815058272969.issue2506@psf.upfronthosting.co.za> |
| 2008年03月29日 21:19:28 | nedbat | link | issue2506 messages |
| 2008年03月29日 21:19:27 | nedbat | create | |