➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author giampaolo.rodola
Recipients brett.cannon, davin, eric.snow, giampaolo.rodola, lukasz.langa, nascheme, osvenskan, pitrou, pmpp, rhettinger, ronaldoussoren, skrah, terry.reedy, yselivanov
Date 2019-02-16.14:48:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1550328529.6.0.0916738536291.issue35813@roundup.psfhosted.org>
In-reply-to
Content 
> 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.
History
Date User Action Args
2019-02-16 14:48:49giampaolo.rodolasetrecipients: + giampaolo.rodola, brett.cannon, nascheme, rhettinger, terry.reedy, ronaldoussoren, pitrou, osvenskan, skrah, pmpp, lukasz.langa, eric.snow, yselivanov, davin
2019-02-16 14:48:49giampaolo.rodolasetmessageid: <1550328529.6.0.0916738536291.issue35813@roundup.psfhosted.org>
2019-02-16 14:48:49giampaolo.rodolalinkissue35813 messages
2019-02-16 14:48:49giampaolo.rodolacreate