Message252805
Did some more testing. KeyboardInterrupt traceback displays properly when pressing Ctrl+C during an infinite loop:
Python 3.5.0 (v3.5.0:374f501f4567, Sep 13 2015, 02:27:37) [MSC v.1900 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> while True:
... pass
...
Traceback (most recent call last):
File "<stdin>", line 2, in <module>
KeyboardInterrupt
>>>
Also when running a file in a similar way as I did in the original bug report:
C:\x>python infinite_loop.py
Traceback (most recent call last):
File "infinite_loop.py", line 2, in <module>
pass
KeyboardInterrupt
C:\x>
Could this mean that the problem is more related to reading stdin than the actual KeyboardInterrupt? |
|
Date |
User |
Action |
Args |
2015-10-11 14:14:49 | mdf | set | recipients:
+ mdf, paul.moore, tim.golden, zach.ware, steve.dower |
2015-10-11 14:14:49 | mdf | set | messageid: <1444572889.07.0.045030112201.issue25376@psf.upfronthosting.co.za> |
2015-10-11 14:14:49 | mdf | link | issue25376 messages |
2015-10-11 14:14:49 | mdf | create | |
|