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 vinay0410
Recipients davin, pitrou, vinay0410
Date 2019-08-04.10:32:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1564914758.61.0.506857998168.issue37754@roundup.psfhosted.org>
In-reply-to
Content
Hi,
I am opening this to discuss about some possible enhancements in the multiprocessing.shared_memory module.

I have recently started using multiprocessing.shared_memory and realised that currently the module provides no functionality to alter the size of the shared memory segment, plus the process has to know beforehand whether to create a segment or open an existing one, unlike shm_open in C, where segment can be automatically created if it doesn't exist.


For an end user perspective I believe that these functionalities would be really helpful, and I would be happy to contribute, if you believe that they are necessary.

I would also like to mention that I agree this might be by design, or because of some challenges, in which case it would be very helpful if I can know them.
History
Date User Action Args
2019-08-04 10:32:38vinay0410setrecipients: + vinay0410, pitrou, davin
2019-08-04 10:32:38vinay0410setmessageid: <1564914758.61.0.506857998168.issue37754@roundup.psfhosted.org>
2019-08-04 10:32:38vinay0410linkissue37754 messages
2019-08-04 10:32:38vinay0410create