On Tue, 22 Jun 2010 08:03:58 am Nick Coghlan wrote: > On Tue, Jun 22, 2010 at 6:16 AM, P.J. Eby <pje at telecommunity.com> wrote: > > True, but making it a separate type with a required encoding gets > > rid of the magical "I don't know" - the "I don't know" encoding is > > just a plain old bytes object. > > So, to boil down the ebytes idea, it is basically a request for a > second string type that holds an octet stream plus an encoding name, > rather than a Unicode character stream. Do any other languages have any equivalent to this ebtyes type? If not, how do they deal with this issue? [...] > This is still smelling an awful lot like the 2.x str type to me Yes. Virtually the only difference I can see is that it lets the user set a per-object default encoding to use when coercing strings to and from bytes. If this is not the case, can somebody please explain what I'm missing? -- Steven D'Aprano
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