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 | pitrou |
|---|---|
| Recipients | benjamin.peterson, gvanrossum, pitrou |
| Date | 2008年06月19日.22:35:19 |
| SpamBayes Score | 0.0010155812 |
| Marked as misclassified | No |
| Message-id | <1213914923.39.0.88719519513.issue3112@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Yet another question. There is a slight discrepancy between tracebacks generated by the builtin-reporting and tracebacks generated by traceback.py. With built-in reporting: Traceback (most recent call last): File "<stdin>", line 1, in <module> File "f.py", line 22, in raise_cause inner_raise_cause() File "f.py", line 13, in inner_raise_cause raise KeyError from e KeyError With traceback.py: Traceback (most recent call last): File "<stdin>", line 1, in <module> File "f.py", line 22, in raise_cause inner_raise_cause() File "f.py", line 13, in inner_raise_cause raise KeyError from e KeyError As you see, indentation of code lines is different. Should we harmonize those behaviours? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年06月19日 22:35:24 | pitrou | set | spambayes_score: 0.00101558 -> 0.0010155812 recipients: + pitrou, gvanrossum, benjamin.peterson |
| 2008年06月19日 22:35:23 | pitrou | set | spambayes_score: 0.00101558 -> 0.00101558 messageid: <1213914923.39.0.88719519513.issue3112@psf.upfronthosting.co.za> |
| 2008年06月19日 22:35:21 | pitrou | link | issue3112 messages |
| 2008年06月19日 22:35:20 | pitrou | create | |