On 19 Jan, 17:06, John Nagle <[EMAIL PROTECTED]> wrote:
> Paul Boddie wrote:
> > Unlike your approach, pprocess employs the fork system call.
>
> Unfortunately, that's not portable. Python's "fork()" is
> "Availability: Macintosh, Unix." I would have preferred
> to use "fork()".
There was a
Paul Boddie wrote:
> Unlike your approach, pprocess employs the fork system call.
Unfortunately, that's not portable. Python's "fork()" is
"Availability: Macintosh, Unix." I would have preferred
to use "fork()".
John Nagle
--
http://mail.python.org/mailma
On 18 Jan, 07:32, John Nagle <[EMAIL PROTECTED]> wrote:
>
> "Processing" is useful, but it uses named pipes and sockets,
> not ordinary pipes. Also, it has C code, so all the usual build
> and version problems apply.
The pprocess module uses pickles over sockets, mostly because the
asynchrono
Carl Banks wrote:
> On Jan 17, 2:28 pm, John Nagle <[EMAIL PROTECTED]> wrote:
>
>> It's also necessary to call Pickle's "clear_memo" before each "dump"
>> call, since objects might change between successive "dump" calls.
>> "Unpickle" doesn't have a "clear_memo" function. It should, because
>> i
On Jan 17, 2:28 pm, John Nagle <[EMAIL PROTECTED]> wrote:
> It's possible to use "pickle" for interprocess communication over
> pipes, but it's not straightforward.
>
> First, "pickle" output is self-delimiting.
> Each dump ends with ".", and, importantly, "load" doesn't read
> any characters after
John Nagle wrote:
> Irmen de Jong wrote:
>> Christian Heimes wrote:
>>> John Nagle wrote:
It's possible to use "pickle" for interprocess communication over
pipes, but it's not straightforward.
Another "gotcha". The "pickle" module seems to be OK with the
translations of "universal n
Irmen de Jong wrote:
> Christian Heimes wrote:
>> John Nagle wrote:
>>> It's possible to use "pickle" for interprocess communication over
>>> pipes, but it's not straightforward.
>>
>> IIRC the processing module uses pickle for IPC. Maybe you can get some
>> idea by reading its code?
>>
>> http://p
Christian Heimes wrote:
> John Nagle wrote:
>> It's possible to use "pickle" for interprocess communication over
>> pipes, but it's not straightforward.
>
> IIRC the processing module uses pickle for IPC. Maybe you can get some
> idea by reading its code?
>
> http://pypi.python.org/pypi/processin
John Nagle wrote:
> It's possible to use "pickle" for interprocess communication over
> pipes, but it's not straightforward.
IIRC the processing module uses pickle for IPC. Maybe you can get some
idea by reading its code?
http://pypi.python.org/pypi/processing/0.40
Christian
--
http://mail.pyt
It's possible to use "pickle" for interprocess communication over
pipes, but it's not straightforward.
First, "pickle" output is self-delimiting.
Each dump ends with ".", and, importantly, "load" doesn't read
any characters after the "." So "pickle" can be used repeatedly
on the same pipe, and on
10 matches
Mail list logo
