psaff...@googlemail.com wrote:
> On 9 Feb, 12:24, Gerhard Häring wrote:
>> http://objectmix.com/python/631346-parallel-python.html
>>
>
> Hmm. In fact, this doesn't seem to work for pp. When I run the code
> below, it says everything is running on the one core.
>
> import pp
> import random
> im
On 9 Feb, 12:24, Gerhard Häring wrote:
> http://objectmix.com/python/631346-parallel-python.html
>
Hmm. In fact, this doesn't seem to work for pp. When I run the code
below, it says everything is running on the one core.
import pp
import random
import time
from string import lowercase
ncpus = 3
On 9 Feb, 12:24, Gerhard Häring wrote:
> Looks like I have answered a similar question once, btw. ;-)
>
Ah, yes - thanks. I did Google for it, but obviously didn't have the
right search term.
Cheers,
Peter
--
http://mail.python.org/mailman/listinfo/python-list
psaff...@googlemail.com wrote:
> Is there some way I can get at this information at run-time? I'd like
> to use it to tag diagnostic output dumped during runs using Parallel
> Python.
There should be a way, but not with the Python standard library. It's
also platform-specific. What are you using?
psaff...@googlemail.com wrote:
> Is there some way I can get at this information at run-time? I'd like
> to use it to tag diagnostic output dumped during runs using Parallel
> Python.
Looks like I have answered a similar question once, btw. ;-)
http://objectmix.com/python/631346-parallel-python.h
Is there some way I can get at this information at run-time? I'd like
to use it to tag diagnostic output dumped during runs using Parallel
Python.
Peter
--
http://mail.python.org/mailman/listinfo/python-list
