Message305048
| Author |
xdegaye |
| Recipients |
brett.cannon, pitrou, serhiy.storchaka, vstinner, xdegaye |
| Date |
2017年10月26日.13:01:35 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1509022895.35.0.213398074469.issue30697@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Checking the test_exceptions test cases that are added by PR 2327 on the current master branch, before the merge of PR 2327:
* test_recursion_normalizing_exception still fails (SIGABRT on a debug build and SIGSEGV otherwise)
* test_recursion_normalizing_infinite_exception is ok as expected
* test_recursion_normalizing_with_no_memory still fails with a SIGSEGV
The attached script except_raises_except.py exercises case 3) described in msg231933. The output is as follows when PR 2327 is applied and confirms that the ResourceWarning is now printed:
Traceback (most recent call last):
File "except_raises_except.py", line 11, in <module>
generator.throw(MyException)
File "except_raises_except.py", line 7, in gen
yield
File "except_raises_except.py", line 3, in __init__
raise MyException
File "except_raises_except.py", line 3, in __init__
raise MyException
File "except_raises_except.py", line 3, in __init__
raise MyException
[Previous line repeated 495 more times]
RecursionError: maximum recursion depth exceeded while calling a Python object
sys:1: ResourceWarning: unclosed file <_io.FileIO name='except_raises_except.py' mode='rb' closefd=True> |
|