Steve Newcomb <s...@coolheads.com> added the comment:

Sometimes a leak is exactly what's wanted, i.e. a standing block of shared 
memory that allows sharing processes come and go ad libitum.  I mention this 
because I haven't seen anyone mention it explicitly.  

While turicas's monkeypatch covers the use case in which a manually-named block 
of shared memory is intended to remain indefinitely, it would be best if future 
versions of shared_memory allowed for such a use case, too.  It shouldn't be 
necessary to monkeypatch in order to have a standing block of shared memory 
remain ready and waiting even when nobody's using it.

----------
nosy: +steve.newcomb

_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue38119>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to