> People keep complaining that they get Unicode errors > when funny characters start showing up in their inputs. > > In some cases, these people would apparantly be happy > if Python would just "keep going", IOW, they want to > get moji-bake (garbled characters), instead of > exceptions that abort their applications. > > I'd like to add a static property unicode.errorhandling, > which defaults to "strict". Applications could set this > to "replace" or "ignore", silencing the errors, and > risking loss of data. > > What do you think? This is a global default, right? Seems to work for the socket timeout; I think the case for a global default is similar. So +eps from me (no more than epsilon because I'm not a Unicode user myself). --Guido van Rossum (home page: http://www.python.org/~guido/)
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