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 draghuram, ethan.furman, mrabarnett, ncoghlan, pitrou, poke, rhettinger, steven.daprano
Date 2010-12-28.12:10:32
SpamBayes Score 2.10814e-06
Marked as misclassified No
Message-id <1293538229.3700.1.camel@localhost.localdomain>
In-reply-to <>
> I'm not sure how that's going to help as I don't want my library code
> to be responsible for printing out exceptions, I just want them to
> print reasonably -- and it seems very unreasonable to have the
> exception I'm converting /from/ show up in the traceback.

I don't know if it's unreasonable. In some cases it can definitely help.
Besides, if you are writing library code (as opposed to application
code), you shouldn't care at all how tracebacks are displayed, should
Date User Action Args
2010-12-28 12:10:34pitrousetrecipients: + pitrou, rhettinger, ncoghlan, draghuram, mrabarnett, steven.daprano, poke, ethan.furman
2010-12-28 12:10:32pitroulinkissue6210 messages
2010-12-28 12:10:32pitroucreate