This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients pitrou, telmich
Date 2012-03-09.14:33:37
SpamBayes Score 5.32261e-10
Marked as misclassified No
Message-id <1331303367.3392.3.camel@localhost.localdomain>
In-reply-to <>
> The problem is *NOT* in the parent: The problem is in the *CHILD* that
> is being called from the shell that is throwing a traceback, which I
> cannot prevent in the python code.

Python does not (at least, should not) run differently as a child or as
a parent. As a matter of fact, any uncaught exception will indeed print
a traceback (which is very useful for e.g. debug purposes). If you don't
want such tracebacks, you can capture stderr in the calling process.

Also, it would be better if you explained your actual case, rather than
complain about specific behaviour.
Date User Action Args
2012-03-09 14:33:38pitrousetrecipients: + pitrou, telmich
2012-03-09 14:33:37pitroulinkissue14228 messages
2012-03-09 14:33:37pitroucreate