Davin Potts <pyt...@discontinuity.net> added the comment:
Apologies, one of the quotes in my previous response should have been attributed to @mental. I think @pierreglaser phrased it very nicely: > shared_memory is a low level python module. Precautions should be made when > handling concurrently the shared_memory objects using synchronization > primitives for example. I'm not sure this should be done internally in the > SharedMemory class -- especially, we don't want to slow down concurrent READ > access. Per the further suggestion: > +1 For a documentation addition. I can take a crack at adding something more along the lines of this discussion, but I would very much welcome suggestions (@bjs, @mental, @pierreglaser)... ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue37652> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
