RetroSearch Browse

Thu Feb 9 13:42:54 CET 2012 · https://mail.python.org/pipermail/python-dev/2012-February/116347.html

On Thu, 9 Feb 2012 08:43:02 +0200
Simon Cross <hodgestar+pythondev at gmail.com> wrote:

> On Thu, Feb 9, 2012 at 2:35 AM, Steven D'Aprano <steve at pearwood.info> wrote:
> > Simon Cross wrote:
> >>
> >> I think I'm -1 on a "locale" encoding because it refers to different
> >> actual encodings depending on where and when it's run, which seems
> >> surprising
> >
> >
> > Why is it surprising? Surely that's the whole point of a locale encoding: to
> > use the locale encoding, whatever that happens to be at the time.
> 
> I think there's a general expectation that if you encode something
> with one codec you will be able to decode it with the same codec.
> That's not necessarily true for the locale encoding.

As And pointed out, this is already the behaviour of the "mbcs" codec
under Windows. "locale" would be the moral (*) equivalent of that under
Unix.

(*) or perhaps immoral :-)

Regards

Antoine.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-February/116347.html below:

[Python-Dev] Add a new "locale" codec?