Why error messages are not getting printed in python3.6?
I've 11 multiprocess pool objects running simultaneously at any time, and there are like 50000 objects in total which will run, but when any of the process throws error like divisionbyzero, and terminates unexpectedly error messages are not getting printed, they only print exception message when the code is under (try : except :)block. I don't understand what is happening here, if anybody could explain me?
python-3.x exception exception-handling multiprocessing try-catch
asked Nov 25 '18 at 3:45
user1779646user1779646
3961414
add a comment |
I've 11 multiprocess pool objects running simultaneously at any time, and there are like 50000 objects in total which will run, but when any of the process throws error like divisionbyzero, and terminates unexpectedly error messages are not getting printed, they only print exception message when the code is under (try : except :)block. I don't understand what is happening here, if anybody could explain me?
python-3.x exception exception-handling multiprocessing try-catch
asked Nov 25 '18 at 3:45
user1779646user1779646
3961414
add a comment |
I've 11 multiprocess pool objects running simultaneously at any time, and there are like 50000 objects in total which will run, but when any of the process throws error like divisionbyzero, and terminates unexpectedly error messages are not getting printed, they only print exception message when the code is under (try : except :)block. I don't understand what is happening here, if anybody could explain me?
python-3.x exception exception-handling multiprocessing try-catch
asked Nov 25 '18 at 3:45
user1779646user1779646
3961414
I've 11 multiprocess pool objects running simultaneously at any time, and there are like 50000 objects in total which will run, but when any of the process throws error like divisionbyzero, and terminates unexpectedly error messages are not getting printed, they only print exception message when the code is under (try : except :)block. I don't understand what is happening here, if anybody could explain me?
python-3.x exception exception-handling multiprocessing try-catch
python-3.x exception exception-handling multiprocessing try-catch
asked Nov 25 '18 at 3:45
user1779646user1779646
3961414
asked Nov 25 '18 at 3:45
user1779646user1779646
3961414
asked Nov 25 '18 at 3:45
user1779646user1779646
3961414
asked Nov 25 '18 at 3:45
user1779646user1779646
3961414
asked Nov 25 '18 at 3:45
user1779646user1779646
3961414
3961414
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This could be as a result of source code that was written before python version 3.
Print statements have been changed to a function since version 3. As a result, when you try to print an error message within an exception catch there might be a syntax error.
Example:
Before Version 3 Update: print "The answer is", 2*2
After: print("The answer is", 2*2)
See official documentation:
https://docs.python.org/3/whatsnew/3.0.html
answered Nov 25 '18 at 3:52
Omer CohenOmer Cohen
11
Well I'm using python 3.6, I think its not showing error messages, because, maybe the new process is overtaking shell fast enough before i could see them.
– user1779646
Nov 25 '18 at 4:00
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f53464480%2fwhy-error-messages-are-not-getting-printed-in-python3-6%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This could be as a result of source code that was written before python version 3.
Print statements have been changed to a function since version 3. As a result, when you try to print an error message within an exception catch there might be a syntax error.
Example:
Before Version 3 Update: print "The answer is", 2*2
After: print("The answer is", 2*2)
See official documentation:
https://docs.python.org/3/whatsnew/3.0.html
answered Nov 25 '18 at 3:52
Omer CohenOmer Cohen
11
Well I'm using python 3.6, I think its not showing error messages, because, maybe the new process is overtaking shell fast enough before i could see them.
– user1779646
Nov 25 '18 at 4:00
add a comment |
This could be as a result of source code that was written before python version 3.
Print statements have been changed to a function since version 3. As a result, when you try to print an error message within an exception catch there might be a syntax error.
Example:
Before Version 3 Update: print "The answer is", 2*2
After: print("The answer is", 2*2)
See official documentation:
https://docs.python.org/3/whatsnew/3.0.html
answered Nov 25 '18 at 3:52
Omer CohenOmer Cohen
11
Well I'm using python 3.6, I think its not showing error messages, because, maybe the new process is overtaking shell fast enough before i could see them.
– user1779646
Nov 25 '18 at 4:00
add a comment |
This could be as a result of source code that was written before python version 3.
Print statements have been changed to a function since version 3. As a result, when you try to print an error message within an exception catch there might be a syntax error.
Example:
Before Version 3 Update: print "The answer is", 2*2
After: print("The answer is", 2*2)
See official documentation:
https://docs.python.org/3/whatsnew/3.0.html
answered Nov 25 '18 at 3:52
Omer CohenOmer Cohen
11
This could be as a result of source code that was written before python version 3.
Print statements have been changed to a function since version 3. As a result, when you try to print an error message within an exception catch there might be a syntax error.
Example:
Before Version 3 Update: print "The answer is", 2*2
After: print("The answer is", 2*2)
See official documentation:
https://docs.python.org/3/whatsnew/3.0.html
answered Nov 25 '18 at 3:52
Omer CohenOmer Cohen
11
answered Nov 25 '18 at 3:52
Omer CohenOmer Cohen
11
answered Nov 25 '18 at 3:52
Omer CohenOmer Cohen
11
answered Nov 25 '18 at 3:52
Omer CohenOmer Cohen
11
11
Well I'm using python 3.6, I think its not showing error messages, because, maybe the new process is overtaking shell fast enough before i could see them.
– user1779646
Nov 25 '18 at 4:00
add a comment |
Well I'm using python 3.6, I think its not showing error messages, because, maybe the new process is overtaking shell fast enough before i could see them.
– user1779646
Nov 25 '18 at 4:00
Well I'm using python 3.6, I think its not showing error messages, because, maybe the new process is overtaking shell fast enough before i could see them.
– user1779646
Nov 25 '18 at 4:00
Well I'm using python 3.6, I think its not showing error messages, because, maybe the new process is overtaking shell fast enough before i could see them.
– user1779646
Nov 25 '18 at 4:00
add a comment |
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.
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%2f53464480%2fwhy-error-messages-are-not-getting-printed-in-python3-6%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
