On 22 August 2014 00:12, Nick Coghlan <ncoghlan at gmail.com> wrote: > On 21 August 2014 23:58, Marko Rauhamaa <marko at pacujo.net> wrote: >> >> My point is that the poor programmer cannot ignore the possibility of >> "funny" character sets. If Python tried to protect the programmer from >> that possibility, the result might be even more intractable: how to act >> on a file with an non-UTF-8 filename if you are unable to express it as >> a text string? > > That's what the "surrogateescape" codec is for Oops, that should say "codec error handled" (I got it right later in the post). Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
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