[issue3138] Hang when calling get() on an empty queue in the queue module

Tuure Laurinolli added the comment: Is it also intended that Queue.get() eats SIGINTs, requiring one to kill the process with something heavier? -- nosy: +tazle ___ Python tracker __

[issue3138] Hang when calling get() on an empty queue in the queue module

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: It's intended that Queue.get blocks until something is put on the Queue. If you don't want it to block use Queue.get(False). -- nosy: +benjamin.peterson resolution: -> invalid status: open -> closed __

[issue3138] Hang when calling get() on an empty queue in the queue module

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: 2.5 has the same behavior: Python 2.5.2 (r252:60911, Feb 21 2008, 13:11:45) [MSC v.1310 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import Queue >>> q = Queue.Queue() >>> q.get() .

[issue3138] Hang when calling get() on an empty queue in the queue module

New submission from Dex <[EMAIL PROTECTED]>: This behavior appears in Python 3.0b1. If you use queue.Queue and call the get method on the empty queue, it appears to hang. The same behavior seems to be evident in the PriorityQueue too. -- messages: 68393 nosy: slash2314 severity: normal