Message116491
| Author |
belopolsky |
| Recipients |
alexandre.vassalotti, amaury.forgeotdarc, belopolsky, collinwinter, eli.bendersky, ezio.melotti, flox, georg.brandl, jyasskin, pitrou, rhettinger, teresap989, terry.reedy |
| Date |
2010年09月15日.21:46:29 |
| SpamBayes Score |
8.654348e-06 |
| Marked as misclassified |
No |
| Message-id |
<AANLkTinGq0qKH6hVjpgWDet2bahQDH1yOye3LJQLcNmC@mail.gmail.com> |
| In-reply-to |
<1284586439.08.0.986395223701.issue9866@psf.upfronthosting.co.za> |
| Content |
On Wed, Sep 15, 2010 at 5:33 PM, Antoine Pitrou <report@bugs.python.org> wrote:
..
> As I said in #9315, I think this kind of thing (bytecode traces) is an implementation detail; the changes
> in results shouldn't be regarded as breaking compatibility.
In r74132, an attempt was made to rationalize and document line
tracing. While it is an implementation detail, I don't think people
expect it to be platform dependent in CPython implementation. "With
computed gotos" was supposed to be a pure optimization. I find it
very surprising that it changes tracing behavior.
> The only problem I could see would be if a whole line of code would be "forgotten".
This is exactly what my example demonstrates. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2010年09月15日 21:46:33 | belopolsky | set | recipients:
+ belopolsky, georg.brandl, collinwinter, rhettinger, terry.reedy, amaury.forgeotdarc, pitrou, alexandre.vassalotti, jyasskin, ezio.melotti, eli.bendersky, flox, teresap989 |
| 2010年09月15日 21:46:31 | belopolsky | link | issue9866 messages |
| 2010年09月15日 21:46:29 | belopolsky | create |
|