[issue32719] fatal error raised when Ctrl-C print loop

2018-03-12 Thread Antoine Pitrou
Antoine Pitrou added the comment: Yes, I don't think this can be fixed in an easy way. Let's say that users will have to live with that. -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker

[issue32719] fatal error raised when Ctrl-C print loop

2018-03-11 Thread Xiang Zhang
Xiang Zhang added the comment: Looks to me it's because the KeyboardInterrupt breaks `_wait_for_thread_shutdown` and reproduces the situation in #23309. @Antonie, do you think anything worth to improve here? Otherwise I'll take this as design. -- nosy: +pitrou

[issue32719] fatal error raised when Ctrl-C print loop

2018-01-29 Thread Xiang Zhang
Xiang Zhang added the comment: It's 3.6 and 3.7. The dir name in traceback doesn't matter. -- ___ Python tracker ___

[issue32719] fatal error raised when Ctrl-C print loop

2018-01-29 Thread Xiang Zhang
New submission from Xiang Zhang : A simple snippet: import threading def func(): while True: print(1,2,3,4,5,6,7,8,9,10) t1 = threading.Thread(target=func) t2 = threading.Thread(target=func) t1.start() t2.start() Running this snippet and Ctrl-C