[issue24512] multiprocessing should log a warning when forking multithreaded process

2015-06-27 Thread Ned Deily

Changes by Ned Deily n...@acm.org:


--
nosy: +davin, sbt
versions: +Python 3.5, Python 3.6 -Python 3.2, Python 3.3

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



[issue24512] multiprocessing should log a warning when forking multithreaded process

2015-06-25 Thread Timothy Cardenas

New submission from Timothy Cardenas:

We were tracking down a bug the other day that was rather hard to find 
involving a forking a process that had both a primary thread and a logging 
thread. The docs clearly state that forking a multithreaded process is 
problematic 
https://docs.python.org/3.4/library/multiprocessing.html#contexts-and-start-methods

However given that it is very simple to check if the process currently has 
multiple threads at the time of the forking operation and that its almost never 
safe to do so with multiple running threads I was wondering if it made sense to 
add a message that warned that a unsafe operation (forking a multithreaded 
process without the forkserver option) was occurring.

--
components: Library (Lib)
messages: 245825
nosy: trcarden
priority: normal
severity: normal
status: open
title: multiprocessing should log a warning when forking multithreaded process
type: enhancement
versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4

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