errors in multiprocessing.shared_memory examples

[pierreglaser]

BPO	36364
Nosy	@brettcannon, @pitrou, @applio, @miss-islington, @pierreglaser
PRs	bpo-36364: fix SharedMemoryManager examples #12439
Files	0001-DOC-fix-SharedMemoryManager-examples.patch

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/applio'
closed_at = None
created_at = <Date 2019-03-19.14:39:57.230>
labels = ['3.8', 'docs']
title = 'errors in multiprocessing.shared_memory examples'
updated_at = <Date 2019-04-02.18:05:40.065>
user = 'https://github.com/pierreglaser'

bugs.python.org fields:

activity = <Date 2019-04-02.18:05:40.065>
actor = 'brett.cannon'
assignee = 'davin'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2019-03-19.14:39:57.230>
creator = 'pierreglaser'
dependencies = []
files = ['48221']
hgrepos = []
issue_num = 36364
keywords = ['patch']
message_count = 5.0
messages = ['338360', '338914', '338915', '339314', '339356']
nosy_count = 6.0
nosy_names = ['brett.cannon', 'pitrou', 'docs@python', 'davin', 'miss-islington', 'pierreglaser']
pr_nums = ['12439']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue36364'
versions = ['Python 3.8']

[pierreglaser]

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.

[miss-islington]

New changeset 3b7e47a by Miss Islington (bot) (Pierre Glaser) in branch 'master':
bpo-36364: fix SharedMemoryManager examples (GH-12439)
3b7e47a

[brettcannon]

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?

[applio]

Very much agreed, they're moving over to the main docs.

[brettcannon]

@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. :)

[furkanonder]

@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. :)

I think issue can be closed.