> On 31 Jan 2022, at 19:22, Dieter Maurer wrote:
>
> Michael Welle wrote at 2022-1-30 09:18 +0100:
>> ...
> The machine this is running on regularly switches
>> its network configuration without restarting the Python application. Now
>> it turns out that the application is still using an old,
I am using multiprocesssing.shared_memory to pass data between NASM and Python.
The shared memory is created in NASM before Python is called. Python connects
to the shm: shm_00 =
shared_memory.SharedMemory(name='shm_object_00',create=False).
I have used shared memory at other points in thi
> On 1 Feb 2022, at 19:21, Michael Welle wrote:
>
> Hello,
>
> Barry writes:
>
On 31 Jan 2022, at 19:22, Dieter Maurer wrote:
>>>
>>> Michael Welle wrote at 2022-1-30 09:18 +0100:
...
>>> The machine this is running on regularly switches
its network configuration without r
> On 1 Feb 2022, at 20:26, Jen Kris via Python-list
> wrote:
>
> I am using multiprocesssing.shared_memory to pass data between NASM and
> Python. The shared memory is created in NASM before Python is called.
> Python connects to the shm: shm_00 =
> shared_memory.SharedMemory(name='shm_
Barry, thanks for your reply.
On the theory that it is not yet possible to pass data from a non-Python
language to Python with multiprocessing.shared_memory, I bypassed the problem
by attaching 4 bytes to my FIFO pipe message from NASM to Python:
byte_val = v[10:14]
where v is the message re
