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 taleinat
Recipients Ido Michael, davin, pitrou, taleinat, vinay0410
Date 2020-02-23.07:44:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1582443853.99.0.57639451577.issue38035@roundup.psfhosted.org>
In-reply-to
Content
I'm not convinced there is enough real need for this to justify implementing and supporting it.

Using shared memory wouldn't be possible with built-in Python objects; one would have to use a special-purpose library for this, or perhaps use something like ctypes. It seems to me that in any case, once someone is doing those, they might as well use those same tools to also create and manage shared resources such as shared memory.

Therefore, even if we allow creating such shared resources, it doesn't seem to me that they will be very usable without a lot of extra supporting features.

In other words, I'd like to see at least one convincing use-case for this before considering any implementation.
History
Date User Action Args
2020-02-23 07:44:14taleinatsetrecipients: + taleinat, pitrou, davin, vinay0410, Ido Michael
2020-02-23 07:44:13taleinatsetmessageid: <1582443853.99.0.57639451577.issue38035@roundup.psfhosted.org>
2020-02-23 07:44:13taleinatlinkissue38035 messages
2020-02-23 07:44:13taleinatcreate