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 terry.reedy
Recipients ezio.melotti, georg.brandl, pitrou, reingart, terry.reedy
Date 2012-10-29.01:09:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1351472960.5.0.839484794547.issue16344@psf.upfronthosting.co.za>
In-reply-to
Content
I am sympathetic with non-English speakers wanting a native-language translation. But I think the interpreter should *always* emit the standard message and that any translation should be an addition, not a replacement. This would maintain discoverablity and help people learn the English version, not hinder it.

The real question to me is how deep in the interpreter such support should go. Third party shells can (and sometimes do) intercept tracebacks and reformat (and translate) as they wish. But there would be advantages and disadvanteges is adding the translation sooner.
History
Date User Action Args
2012-10-29 01:09:20terry.reedysetrecipients: + terry.reedy, georg.brandl, pitrou, ezio.melotti, reingart
2012-10-29 01:09:20terry.reedysetmessageid: <1351472960.5.0.839484794547.issue16344@psf.upfronthosting.co.za>
2012-10-29 01:09:20terry.reedylinkissue16344 messages
2012-10-29 01:09:20terry.reedycreate