On approximately 5/6/2009 10:53 PM, came the following characters from the keyboard of Martin v. Löwis: >> The error handler designed with utf-8 in mind has no name in the encode >> direction and is called "utf_8b_decoder_invalid_bytes" in the decode >> direction. By your reasoning, *that* should be its name in Python. The >> encoding error handler would then be named analogously >> "utf_8b_encoder_invalid_codepoints". Even these, to me, would be better >> than confusing giving them the same name as the codec. > > So are you proposing that I should rename the PEP 383 handler > to "utf_8b_encoder_invalid_codepoints"? No, he's saying that your algorithm for choosing the PEP 383 handler should have come up with that name, rather than utf8b. But since PEP 383 applies to other codecs besides UTF-8, it should have a different name. And one that is less cumbersome than "utf_8b_encoder_invalid_codepoints" -- Glenn -- http://nevcal.com/ =========================== A protocol is complete when there is nothing left to remove. -- Stuart Cheshire, Apple Computer, regarding Zero Configuration Networking
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