On 01/13/2014 09:31 AM, Antoine Pitrou wrote: > On Mon, 13 Jan 2014 08:36:05 -0800 > Ethan Furman wrote: >> >> You mean crash all the time? I'd be fine with that for both the str case >> and the bytes case. But's probably too late >> to change the str case, and the bytes case should mirror what str does. > > Let me add something else: str and bytes don't have to be symmetrical. > In Python 2, str and unicode were symmetrical, they allowed exactly the > same operations and were composable. > In Python 3, str and bytes are different beasts; they have different > operations *and* different semantics (for example, bytes interoperates > with bytearray and memoryview, while str doesn't). This makes sense to me. So I'm guess I'm fine with either the quoted ascii repr or the always blowing up method, with leaning towards the blowing up method. -- ~Ethan~
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