Issue 36364: errors in multiprocessing.shared_memory examples (original) (raw)

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/80545

classification

Title: errors in multiprocessing.shared_memory examples
Type: Stage: patch review
Components: Documentation Versions: Python 3.8

process

Status: open Resolution:
Dependencies: Superseder:
Assigned To: davin Nosy List: brett.cannon, davin, docs@python, miss-islington, pierreglaser, pitrou
Priority: normal Keywords: patch

Created on 2019-03-19 14:39 by pierreglaser, last changed 2022-04-11 14:59 by admin.

Files
File name Uploaded Description Edit
0001-DOC-fix-SharedMemoryManager-examples.patch pierreglaser,2019-03-19 14:39
Pull Requests
URL Status Linked Edit
PR 12439 merged pierreglaser,2019-03-19 14:44
Messages (5)
msg338360 - (view) Author: Pierre Glaser (pierreglaser) * Date: 2019-03-19 14:39
The examples of the new shared_memory module using SharedMemoryManager try to import the class from multiprocessing.shared_memory instead of multiprocessing.managers, making them fail.
msg338914 - (view) Author: miss-islington (miss-islington) Date: 2019-03-26 19:12
New changeset 3b7e47aea9b29f2669e7178a461426d18bce349e by Miss Islington (bot) (Pierre Glaser) in branch 'master': bpo-36364: fix SharedMemoryManager examples (GH-12439) https://github.com/python/cpython/commit/3b7e47aea9b29f2669e7178a461426d18bce349e
msg338915 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2019-03-26 19:13
I've gone ahead and merged Pierre's fix (thanks!), but I'm not sure if SharedMemoryManager should stay in the shared_memory docs or if it should move over to multiprocessing.manager. Davin, any input on that?
msg339314 - (view) Author: Davin Potts (davin) * (Python committer) Date: 2019-04-02 03:37
Very much agreed, they're moving over to the main docs.
msg339356 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2019-04-02 18:05
@Davin is there an issue for that and thus this issue can then be closed? Or did you want to re-purpose this issue to track that? Either way I'm assigning the issue to you to let you decide which way you want to go. :)
History
Date User Action Args
2022-04-11 14:59:12 admin set github: 80545
2019-04-02 18:05:40 brett.cannon set assignee: docs@python -> davinmessages: +
2019-04-02 03:37:38 davin set messages: +
2019-03-26 19:13:44 brett.cannon set nosy: + brett.cannonmessages: +
2019-03-26 19:12:49 miss-islington set nosy: + miss-islingtonmessages: +
2019-03-19 15:04:10 xtreak set nosy: + pitrou, davin
2019-03-19 14:44:24 pierreglaser set stage: patch reviewpull_requests: + <pull%5Frequest12394>
2019-03-19 14:39:57 pierreglaser create