On 29 March 2017 at 00:40, Terry Reedy wrote:
> [. . .] Eryk Sun suggested a patch for Windows, (and
> the possibility of using pthread_kill). Can you possibly do one for *nix?
> This is out of my ballpark, but the bug (relative to console behavior) is a
> nuisance.
I'll try
Steven, thanks for verifying bug on *nix.
On 3/28/2017 2:00 AM, Martin Panter wrote:
On 28 March 2017 at 03:11, Steven D'Aprano wrote:
On Mon, Mar 27, 2017 at 10:33:44PM -0400, Terry Reedy wrote:
https://bugs.python.org/issue29926 was opened as an IDLE issue, which
means
On 28 March 2017 at 03:11, Steven D'Aprano wrote:
> On Mon, Mar 27, 2017 at 10:33:44PM -0400, Terry Reedy wrote:
>> https://bugs.python.org/issue29926 was opened as an IDLE issue, which
>> means that most watching the new issues list would ignore it. But I
>> think it is an
On Mon, Mar 27, 2017 at 10:33:44PM -0400, Terry Reedy wrote:
> https://bugs.python.org/issue29926 was opened as an IDLE issue, which
> means that most watching the new issues list would ignore it. But I
> think it is an issue with _thread.interrupt_main (which IDLE calls in
> respond to ^C)
https://bugs.python.org/issue29926 was opened as an IDLE issue, which
means that most watching the new issues list would ignore it. But I
think it is an issue with _thread.interrupt_main (which IDLE calls in
respond to ^C) not interrupting time.sleep(n) in main thread*. I tested
on Windows,