[issue40815] Multiprocessing docs don't describe thread-safety

[Irit Katriel]

Irit Katriel  added the comment:

Probably another example: issue41567

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40815] Multiprocessing docs don't describe thread-safety

[Irit Katriel]

Irit Katriel  added the comment:

Here's an example where such documentation may have helped: 
https://bugs.python.org/issue40860

--
nosy: +iritkatriel

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40815] Multiprocessing docs don't describe thread-safety

[Alan Briolat]

Change by Alan Briolat :


--
nosy: +alan.briolat

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40815] Multiprocessing docs don't describe thread-safety

[Ben]

New submission from Ben :

The Multiprocessing docs specifically say that Queue is process- and thread- 
safe: 
https://docs.python.org/3/library/multiprocessing.html#exchanging-objects-between-processes.

But this information is not given for the various synchronisation primitives 
and such (Lock, Semaphore, Event, etc)

Are they thread-safe?  Should the docs say whether they are or are not?

--
assignee: docs@python
components: Documentation
messages: 370310
nosy: bjs, docs@python
priority: normal
severity: normal
status: open
title: Multiprocessing docs don't describe thread-safety

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com