[issue11361] suggestion for os.kill(pid,CTRL_C_EVENT) in tests

2021-02-26 Thread Eryk Sun
Change by Eryk Sun : -- versions: +Python 3.10, Python 3.8, Python 3.9 -Python 2.7, Python 3.4, Python 3.5, Python 3.6 ___ Python tracker ___

[issue11361] suggestion for os.kill(pid,CTRL_C_EVENT) in tests

2016-02-13 Thread Giampaolo Rodola'
Changes by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___

[issue11361] suggestion for os.kill(pid,CTRL_C_EVENT) in tests

2015-12-05 Thread Eryk Sun
Eryk Sun added the comment: test_CTRL_C_EVENT can be removed from Lib/test/test_os.py. It's of no practical consequence. Ctrl+Break is always enabled in the child process, so test_CTRL_BREAK_EVENT should remain. When using CREATE_NEW_PROCESS_GROUP, the child process is started with Ctrl+C

[issue11361] suggestion for os.kill(pid,CTRL_C_EVENT) in tests

2014-07-09 Thread Mark Lawrence
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- versions: +Python 3.4, Python 3.5 -Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11361 ___

[issue11361] suggestion for os.kill(pid,CTRL_C_EVENT) in tests

2014-07-09 Thread Gregory P. Smith
Gregory P. Smith added the comment: (un-cc'ing myself as I can't deal with Windows) -- components: +Tests, Windows -IO ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11361 ___

[issue11361] suggestion for os.kill(pid,CTRL_C_EVENT) in tests

2014-07-09 Thread Gregory P. Smith
Changes by Gregory P. Smith g...@krypto.org: -- nosy: -gregory.p.smith ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11361 ___ ___

[issue11361] suggestion for os.kill(pid,CTRL_C_EVENT) in tests

2011-05-02 Thread STINNER Victor
STINNER Victor victor.stin...@haypocalc.com added the comment: http://www.python.org/dev/buildbot/all/builders/x86%20XP-4%203.x/builds/4483/steps/test/logs/stdio -- test test_os failed -- Traceback (most recent call last): File

[issue11361] suggestion for os.kill(pid,CTRL_C_EVENT) in tests

2011-05-01 Thread STINNER Victor
STINNER Victor victor.stin...@haypocalc.com added the comment: Oh, if the process is able to handle CTRL+c on Windows, it means that faulthandler.register() could be used on Windows. While developing the faulthandler module, I tried all signals but I was only able to handle SIGSEGV, SIGABRT,

[issue11361] suggestion for os.kill(pid,CTRL_C_EVENT) in tests

2011-04-30 Thread STINNER Victor
Changes by STINNER Victor victor.stin...@haypocalc.com: -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11361 ___ ___

[issue11361] suggestion for os.kill(pid,CTRL_C_EVENT) in tests

2011-04-29 Thread Brian Curtin
Changes by Brian Curtin br...@python.org: -- assignee: - brian.curtin nosy: +brian.curtin ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11361 ___

[issue11361] suggestion for os.kill(pid,CTRL_C_EVENT) in tests

2011-03-04 Thread Terry J. Reedy
Changes by Terry J. Reedy tjre...@udel.edu: -- title: suggestion for os.kill(pid,CTRL_C_EVENT) - suggestion for os.kill(pid,CTRL_C_EVENT) in tests ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11361