Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #46259 > unrolled thread

Re: Python error codes and messages location

Started byFábio Santos <fabiosantosart@gmail.com>
First post2013-05-28 07:57 +0100
Last post2013-05-28 07:57 +0100
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Python error codes and messages location Fábio Santos <fabiosantosart@gmail.com> - 2013-05-28 07:57 +0100

#46259 — Re: Python error codes and messages location

FromFábio Santos <fabiosantosart@gmail.com>
Date2013-05-28 07:57 +0100
SubjectRe: Python error codes and messages location
Message-ID<mailman.2283.1369724237.3114.python-list@python.org>

[Multipart message — attachments visible in raw view] — view raw

On 28 May 2013 05:17, "Vito De Tullio" <vito.detullio@gmail.com> wrote:
>
> Fábio Santos wrote:
>
> >> > > Speaking of PEPs and exceptions. When do we get localized
exceptions?
> >> >
> >> > What do you mean by "localized exceptions"?
> >> >
> >> > Please, tell me it's *NOT* a proposal to send the exception message
in
> >> > the
> >> > locale language!
> >> It is. I think I read it mentioned in python-dev or this list.
> >
> > Here is what I read.
> >
> > http://mail.python.org/pipermail/python-dev/2013-April/125364.html
> >
> > It wasn't only about exceptions after all. And it seems like something
> > that will only happen far into the future.
>
> I really hope really far... have you never tried to google a localized
error
> message? :\
>
> --
> By ZeD
>

Never. I don't even try.

I still think this is a good idea. Not for debugging though.

For UI (and error logs if your requirements include writing them in the
user language), it could simplify all the
user-facing-unexpected-error-reporting into an except hook, or a
try..except high up in your call stack.

It would be a pretty big step towards RAD. But it had to be made optional
somehow.

Maybe using errno and existing exception messages together with gettext?

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web