On Tue, May 28, 2013 at 6:10 PM, Fábio Santos <fabiosantos...@gmail.com> wrote: > Just to clarify, I am suggesting to have the unchanged messages in > tracebacks, but having some methods in the exception to get the exception > and message localised. Just like repr() and str() are directed at different > audiences (the programmer vs. The user), so is a traceback vs a message box.
There's no particular reason for that to be a method on the exception, then. You're just asking to localize a text string, and I think that functionality already exists someplace :) > OpenERP for example shows stack traces to the user. It could show a shorter > message in the user's language. Sounds like an OpenERP feature request, then. > On 28 May 2013 08:19, "Chris Angelico" <ros...@gmail.com> wrote: >> Can we internationalize English instead of localizing Python? >> > > That is worse than saying, "why don't we all just code in python?". Or c. Or > java. Or JavaScript. > > Let's not get into that. I prefer len() to new > LengthCalculatorFactoryBuilder().createLengthCalculatorFactory().createLengthCalculator().calculateLengthOf(). > And a good old Python list or JavaScript array to a collection of segfaults. Yeah, like I said, that wasn't a serious suggestion :) ChrisA -- http://mail.python.org/mailman/listinfo/python-list
