M.-A. Lemburg wrote: > Hmm, I would assume that application authors do have the > proper permissions to use the work-around I mentioned > below, that is, add sitecustomize.py to their application > as top-level module and change the default encoding to > use their custom codec instead. But that would interfere with a sitecustomize.py already present on the system. > Then again, if you only change the ASCII codec, you wouldn't > have to change these hard coded "strict" values. Why not? If the argument parser invokes the default encoding, and passes "strict", then this would override the default error handling of the codec, no? 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