Gregory P. Smith <greg <at> krypto.org> writes: > Given the existing brokenness I personally think that removing the BOM insertion (because it is incorrect) in 2.7 and 3.2 is fine if you cannot find a way to make it correct in 2.7 and 3.2 without breaking existing APIs. I have an idea for a change which won't require changing any public APIs; though it does change the behaviour so that BOM insertion doesn't happen any more, anyone who needs a BOM can have it by a simple update to their format string. The idea is outlined here: http://bugs.python.org/issue14452#msg158030 Comments would be appreciated. Regards, Vinay Sajip
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