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 paul.moore
Recipients Kallah, eryksun, paul.moore, steve.dower, steven.daprano, tim.golden, zach.ware
Date 2020-01-08.17:13:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1578503619.96.0.777167799638.issue39255@roundup.psfhosted.org>
In-reply-to
Content
Agreed it's not a bug, but I will say it took me a while to work out *why* it's not a bug (namely, that even though the OP is using shared memory values, the code relies on fork semantics to share the two Value objects that *reference* the shared memory).

It would be worth adding a note to the documentation on shared memory values at https://docs.python.org/3.8/library/multiprocessing.html#sharing-state-between-processes to make it clearer that it's the user's responsibility to make sure the Value object is passed to every subprocess that wants to interact with it.
History
Date User Action Args
2020-01-08 17:13:40paul.mooresetrecipients: + paul.moore, tim.golden, steven.daprano, zach.ware, eryksun, steve.dower, Kallah
2020-01-08 17:13:39paul.mooresetmessageid: <1578503619.96.0.777167799638.issue39255@roundup.psfhosted.org>
2020-01-08 17:13:39paul.moorelinkissue39255 messages
2020-01-08 17:13:39paul.moorecreate