Davin Potts added the comment:
This issue was marked as not a bug by OP a while back but for whatever reason
it did not also get marked as closed. Going ahead with closing it now.
--
nosy: +davin
stage: needs patch - resolved
status: open - closed
Brian Quinlan added the comment:
OK, working as intended.
--
resolution: - invalid
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7200
___
___
Ask Solem a...@opera.com added the comment:
Queue uses multiprocessing.util.Finalize, which uses weakrefs to track when the
object is out of scope, so this is actually expected behavior.
IMHO it is not a very good approach, but changing the API to use explicit close
methods is a little late
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
assignee: - jnoller
nosy: +jnoller
stage: - needs patch
versions: +Python 2.7, Python 3.1
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7200
New submission from Brian Quinlan br...@sweetapp.com:
This code:
import multiprocessing
import queue
def _process_worker(q):
while True:
try:
something = q.get(block=True, timeout=0.1)
except queue.Empty:
return
else:
pass
