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 | ajaksu2 |
|---|---|
| Recipients | ajaksu2, theller |
| Date | 2008年04月03日.15:51:11 |
| SpamBayes Score | 0.13281436 |
| Marked as misclassified | No |
| Message-id | <1207237875.11.0.615915047809.issue2542@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The tests pass and prints the ignores. But I still see an issue: import sys def g(): try: return g() except: return sys.exc_info() >>> g() (<type 'exceptions.RuntimeError'>, 'maximum recursion depth exceeded while calling a Python object', <traceback object at 0xb7d3d75c>) >>> import sys Traceback (most recent call last): File "<stdin>", line 1, in <module> RuntimeError: maximum recursion depth exceeded Then, I can raise that RuntimeError and clear things: >>> sys.excepthook(*g()) Traceback (most recent call last): File "<stdin>", line 3, in g RuntimeError: maximum recursion depth exceeded while calling a Python object >>> import sys >>> The attached patch adds a test for this condition, I hope someone more test-savvy than I can review it. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年04月03日 15:51:15 | ajaksu2 | set | spambayes_score: 0.132814 -> 0.13281436 recipients: + ajaksu2, theller |
| 2008年04月03日 15:51:15 | ajaksu2 | set | spambayes_score: 0.132814 -> 0.132814 messageid: <1207237875.11.0.615915047809.issue2542@psf.upfronthosting.co.za> |
| 2008年04月03日 15:51:13 | ajaksu2 | link | issue2542 messages |
| 2008年04月03日 15:51:12 | ajaksu2 | create | |