[issue1360] Queue.get() can't be interrupted with Ctrl-C unless timed out

2017-06-15 Thread Roundup Robot
Changes by Roundup Robot : -- pull_requests: +2268 ___ Python tracker ___

[issue1360] Queue.get() can't be interrupted with Ctrl-C unless timed out

2017-06-13 Thread Guido van Rossum
Guido van Rossum added the comment: This issue is closed, but you can open a new issue to flag this in the docs. -- ___ Python tracker ___

[issue1360] Queue.get() can't be interrupted with Ctrl-C unless timed out

2017-06-13 Thread Stephen Rosen
Stephen Rosen added the comment: Can a note be added to the Queue.get() documentation? This behavior has been known to be at least potentially confusing for a decade, and there's no mention of it in the documentation. -- nosy: +Stephen Rosen versions: +Python 2.7 -Python 2.5

[issue1360] Queue.get() can't be interrupted with Ctrl-C unless timed out

2012-04-04 Thread Matt Joiner
Matt Joiner anacro...@gmail.com added the comment: Isn't this fixed in Python=3.2? -- nosy: +anacrolix ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1360 ___

[issue1360] Queue.get() can't be interrupted with Ctrl-C unless timed out

2007-10-29 Thread Daniele Varrazzo
New submission from Daniele Varrazzo: This issue probably depends on #1167930 When waiting on a queue in blocking mode, in no timeout is set, ctrl-C doesn't raise KeyboardInterrupt:: q = Queue() q.get(True) # ctrl-c doesn't work here If any timeout is set, ctrl-c works as

[issue1360] Queue.get() can't be interrupted with Ctrl-C unless timed out

2007-10-29 Thread Guido van Rossum
Guido van Rossum added the comment: This (and the other issue you mention) is because the regular acquire() method on a basic lock cannot be interrupted. That's unlikely to go away, so you'll just have to live with this. As you've discovered, specifying a timeout solves the issue. Since code

[issue1360] Queue.get() can't be interrupted with Ctrl-C unless timed out

2007-10-29 Thread Daniele Varrazzo
Daniele Varrazzo added the comment: Because the easy workaround, we can live with the issue. Anyway, because the workaround is not trivial to find, and because the behavior is supposed to remain unchanged, maybe the issue should be mentioned in the docs. Thank you for the explanation :)