M.-A. Lemburg wrote: > But if you change the default behaviour of the builtin codecs > only, how would this help a user of a broken application ? It would be even sufficient to change the behaviour of the us-ascii codec, as this is the default codec. The user of the broken implementation would get question marks in places that would previously cause an exception. That may be acceptable, if it is only debugging output or log files; it may be tolerable if this is only for text seen by users. > The Unicode implementation would continue to use "strict" > for things like low-level parser marker conversions and external > codecs would also not work as expected (e.g. the Asian codecs). Sure, but they would also not be the default codecs. Not sure what "low-level parser marker conversions" are: what is a "parser marker"? > In the end, I don't think we'd gain anything much except another > global to carry around. It will make developers happier, as they need less urgently fix applications that blow up at the customer. Regards, Martin
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