A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2000-May/003895.html below:

[I18n-sig] Re: [Python-Dev] Unicode debate

[I18n-sig] Re: [Python-Dev] Unicode debate [I18n-sig] Re: [Python-Dev] Unicode debatePaul Prescod paul@prescod.net
Tue, 02 May 2000 13:23:24 -0500
Guido van Rossum wrote:
> 
> ....
> 
> Have you tried using this?

Yes. I haven't had large problems with it.

As long as you know what is going on, it doesn't usually hurt anything
because you can just explicitly set up the decoding you want. It's like
the int division problem. You get bitten a few times and then get
careful.

It's the naive user who will be surprised by these random UTF-8 decoding
errors. 

That's why this is NOT a convenience issue (are you listening MAL???).
It's a short and long term simplicity issue. There are lots of languages
where it is de rigeur to discover and work around inconvenient and
confusing default behaviors. I just don't think that we should be ADDING
such behaviors.

-- 
 Paul Prescod  - ISOGEN Consulting Engineer speaking for himself
It's difficult to extract sense from strings, but they're the only
communication coin we can count on. 
	- http://www.cs.yale.edu/~perlis-alan/quotes.html



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4