[Python-Dev] [PEP 3148] futures - execute computations asynchronously (original) (raw)
Jesse Noller jnoller at gmail.com
Sat Mar 6 22:58:19 CET 2010
- Previous message: [Python-Dev] [PEP 3148] futures - execute computations asynchronously
- Next message: [Python-Dev] [PEP 3148] futures - execute computations asynchronously
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mar 6, 2010, at 4:20 PM, Dj Gilcrease <digitalxero at gmail.com> wrote:
I have been playing with the feedback branch of this package for py3 and there seems to be a rather serious bug in the Process version. Using the code @ http://dpaste.com/hold/168795/
When I was running in debug mode I found that as soon as p = multiprocessing.Process( target=processworker, args=(self.callqueue, self.resultqueue, self.shutdownprocessevent)) was called (yes even before p.start() was called) the processes just started launching all by themselves.
Did you run the provided example code on windows by chance? If so,
look at the multiprocessing docs, there are restrictions on windows
(see the main note) - not following the guidelines can result in
lots of processes spawning.
- Previous message: [Python-Dev] [PEP 3148] futures - execute computations asynchronously
- Next message: [Python-Dev] [PEP 3148] futures - execute computations asynchronously
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]