On Sep 3, 2011, at 2:03 PM, Massimo Di Pierro wrote: > Yes and no. > > The new scheduler uses multiprocessing to make sure each task is > executed in its on process. This allows the main process to monitor > the task and eventually terminate it. It also prevents a task from > messing up the worker status. > > Windows does not support work and multiprocessing behaves very > strangely. Instead of duplicating the memory space (what fork does on > linux) it re-creates it but re-running all the imports. The process > running the task should not have access to current because it may run > a task from another app. > > So the bottom line is, we could have a single import current on top > but I do not understand multiprocessing on windows well enough to be > sure it is safe.
I'd think it'd be as safe as your static imports of loads & dumps. > > Massimo > >> Is there any reason that current can't be imported statically at the head of >> the file? I wouldn't have thought so. (Of course, that doesn't explain the >> 'invalid json' error.
