[issue35813] shared memory construct to avoid need for serialization between processes
Giampaolo Rodola'
report at bugs.python.org
Sat Feb 16 09:48:49 EST 2019
Giampaolo Rodola' <g.rodola at gmail.com> added the comment:
> Because shared memory blocks are not "owned" by a single process...
> [...]
> I propose a simpler, consistent-across-platforms API like:
> SharedMemory(name=None, create=False, size=0)
Maybe something like this instead?
SharedMemory(name=None, attach_if_exists=False, size=0)
The use case I'm thinking about is 2 distinct processes/apps which agree on a common fixed name.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35813>
_______________________________________
More information about the Python-bugs-list
mailing list