Display warnning only once using python multiprocessing
up vote
0
down vote
favorite
Is there a way to display a warning only once when using Pythons multiprocessing.Pool?
Simple example that illustrates the problem
import multiprocessing
import warnings
def func_with_warning(data):
warnings.warn("Warning message ".format(data))
if __name__ == '__main__':
data = [0, 1, 2]
pool = multiprocessing.Pool(2)
pool.map(func_with_warning, data)
Result:
>> /home/user/script.py:10: UserWarning: Warning message 0
warnings.warn("Warning message ".format(data))
/home/user/script.py:10: UserWarning: Warning message 1
warnings.warn("Warning message ".format(data))
/home/user/script.py:10: UserWarning: Warning message 2
warnings.warn("Warning message ".format(data))
>>
I understand that each spawned process is like separate Python world, but maybe someone knows any trick how to display warnings in such cases only once?
Someone suggested it is duplicate of question: Python 3: Catching warnings during multiprocessing. In my opinion:
- it is similar, but not the same.
- solutions there may, but do not have to answer my question,
- it is much more detailed and focused on some narrower scope problem of catching warnings during objects instantiations
python python-3.x warnings python-multiprocessing
add a comment |
up vote
0
down vote
favorite
Is there a way to display a warning only once when using Pythons multiprocessing.Pool?
Simple example that illustrates the problem
import multiprocessing
import warnings
def func_with_warning(data):
warnings.warn("Warning message ".format(data))
if __name__ == '__main__':
data = [0, 1, 2]
pool = multiprocessing.Pool(2)
pool.map(func_with_warning, data)
Result:
>> /home/user/script.py:10: UserWarning: Warning message 0
warnings.warn("Warning message ".format(data))
/home/user/script.py:10: UserWarning: Warning message 1
warnings.warn("Warning message ".format(data))
/home/user/script.py:10: UserWarning: Warning message 2
warnings.warn("Warning message ".format(data))
>>
I understand that each spawned process is like separate Python world, but maybe someone knows any trick how to display warnings in such cases only once?
Someone suggested it is duplicate of question: Python 3: Catching warnings during multiprocessing. In my opinion:
- it is similar, but not the same.
- solutions there may, but do not have to answer my question,
- it is much more detailed and focused on some narrower scope problem of catching warnings during objects instantiations
python python-3.x warnings python-multiprocessing
Use a shared flag or aqueue
.
– stovfl
Nov 8 at 16:03
You should surround the work with the pool inif __name__ == '__main__':
clause. See this for detail
– Artemiy
Nov 8 at 18:51
@stovfl So in shared memory I need to keep track of every possible warning I am displaying and check before warning? Sounds like a lot of work and additional code, it is some solution, but only for warnings I raise myself. For warnings raised by libraries I use I think it won't work.
– dankal444
Nov 9 at 20:36
@Artemly I guess you tried to run the example while being on Windows, I am using Linux and when I wrote this simple example I forgot about this fork-problem you encountered. I will edit post
– dankal444
Nov 9 at 20:40
Possible duplicate of Python 3: Catching warnings during multiprocessing
– stovfl
Nov 9 at 21:11
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Is there a way to display a warning only once when using Pythons multiprocessing.Pool?
Simple example that illustrates the problem
import multiprocessing
import warnings
def func_with_warning(data):
warnings.warn("Warning message ".format(data))
if __name__ == '__main__':
data = [0, 1, 2]
pool = multiprocessing.Pool(2)
pool.map(func_with_warning, data)
Result:
>> /home/user/script.py:10: UserWarning: Warning message 0
warnings.warn("Warning message ".format(data))
/home/user/script.py:10: UserWarning: Warning message 1
warnings.warn("Warning message ".format(data))
/home/user/script.py:10: UserWarning: Warning message 2
warnings.warn("Warning message ".format(data))
>>
I understand that each spawned process is like separate Python world, but maybe someone knows any trick how to display warnings in such cases only once?
Someone suggested it is duplicate of question: Python 3: Catching warnings during multiprocessing. In my opinion:
- it is similar, but not the same.
- solutions there may, but do not have to answer my question,
- it is much more detailed and focused on some narrower scope problem of catching warnings during objects instantiations
python python-3.x warnings python-multiprocessing
Is there a way to display a warning only once when using Pythons multiprocessing.Pool?
Simple example that illustrates the problem
import multiprocessing
import warnings
def func_with_warning(data):
warnings.warn("Warning message ".format(data))
if __name__ == '__main__':
data = [0, 1, 2]
pool = multiprocessing.Pool(2)
pool.map(func_with_warning, data)
Result:
>> /home/user/script.py:10: UserWarning: Warning message 0
warnings.warn("Warning message ".format(data))
/home/user/script.py:10: UserWarning: Warning message 1
warnings.warn("Warning message ".format(data))
/home/user/script.py:10: UserWarning: Warning message 2
warnings.warn("Warning message ".format(data))
>>
I understand that each spawned process is like separate Python world, but maybe someone knows any trick how to display warnings in such cases only once?
Someone suggested it is duplicate of question: Python 3: Catching warnings during multiprocessing. In my opinion:
- it is similar, but not the same.
- solutions there may, but do not have to answer my question,
- it is much more detailed and focused on some narrower scope problem of catching warnings during objects instantiations
python python-3.x warnings python-multiprocessing
python python-3.x warnings python-multiprocessing
edited Nov 11 at 15:38
asked Nov 8 at 11:11
dankal444
145113
145113
Use a shared flag or aqueue
.
– stovfl
Nov 8 at 16:03
You should surround the work with the pool inif __name__ == '__main__':
clause. See this for detail
– Artemiy
Nov 8 at 18:51
@stovfl So in shared memory I need to keep track of every possible warning I am displaying and check before warning? Sounds like a lot of work and additional code, it is some solution, but only for warnings I raise myself. For warnings raised by libraries I use I think it won't work.
– dankal444
Nov 9 at 20:36
@Artemly I guess you tried to run the example while being on Windows, I am using Linux and when I wrote this simple example I forgot about this fork-problem you encountered. I will edit post
– dankal444
Nov 9 at 20:40
Possible duplicate of Python 3: Catching warnings during multiprocessing
– stovfl
Nov 9 at 21:11
add a comment |
Use a shared flag or aqueue
.
– stovfl
Nov 8 at 16:03
You should surround the work with the pool inif __name__ == '__main__':
clause. See this for detail
– Artemiy
Nov 8 at 18:51
@stovfl So in shared memory I need to keep track of every possible warning I am displaying and check before warning? Sounds like a lot of work and additional code, it is some solution, but only for warnings I raise myself. For warnings raised by libraries I use I think it won't work.
– dankal444
Nov 9 at 20:36
@Artemly I guess you tried to run the example while being on Windows, I am using Linux and when I wrote this simple example I forgot about this fork-problem you encountered. I will edit post
– dankal444
Nov 9 at 20:40
Possible duplicate of Python 3: Catching warnings during multiprocessing
– stovfl
Nov 9 at 21:11
Use a shared flag or a
queue
.– stovfl
Nov 8 at 16:03
Use a shared flag or a
queue
.– stovfl
Nov 8 at 16:03
You should surround the work with the pool in
if __name__ == '__main__':
clause. See this for detail– Artemiy
Nov 8 at 18:51
You should surround the work with the pool in
if __name__ == '__main__':
clause. See this for detail– Artemiy
Nov 8 at 18:51
@stovfl So in shared memory I need to keep track of every possible warning I am displaying and check before warning? Sounds like a lot of work and additional code, it is some solution, but only for warnings I raise myself. For warnings raised by libraries I use I think it won't work.
– dankal444
Nov 9 at 20:36
@stovfl So in shared memory I need to keep track of every possible warning I am displaying and check before warning? Sounds like a lot of work and additional code, it is some solution, but only for warnings I raise myself. For warnings raised by libraries I use I think it won't work.
– dankal444
Nov 9 at 20:36
@Artemly I guess you tried to run the example while being on Windows, I am using Linux and when I wrote this simple example I forgot about this fork-problem you encountered. I will edit post
– dankal444
Nov 9 at 20:40
@Artemly I guess you tried to run the example while being on Windows, I am using Linux and when I wrote this simple example I forgot about this fork-problem you encountered. I will edit post
– dankal444
Nov 9 at 20:40
Possible duplicate of Python 3: Catching warnings during multiprocessing
– stovfl
Nov 9 at 21:11
Possible duplicate of Python 3: Catching warnings during multiprocessing
– stovfl
Nov 9 at 21:11
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53206568%2fdisplay-warnning-only-once-using-python-multiprocessing%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Use a shared flag or a
queue
.– stovfl
Nov 8 at 16:03
You should surround the work with the pool in
if __name__ == '__main__':
clause. See this for detail– Artemiy
Nov 8 at 18:51
@stovfl So in shared memory I need to keep track of every possible warning I am displaying and check before warning? Sounds like a lot of work and additional code, it is some solution, but only for warnings I raise myself. For warnings raised by libraries I use I think it won't work.
– dankal444
Nov 9 at 20:36
@Artemly I guess you tried to run the example while being on Windows, I am using Linux and when I wrote this simple example I forgot about this fork-problem you encountered. I will edit post
– dankal444
Nov 9 at 20:40
Possible duplicate of Python 3: Catching warnings during multiprocessing
– stovfl
Nov 9 at 21:11