> How so? In theory, all the ways you write string constructors today > would eventually map to Unicode objects. I'm thinking of string > literals and constructor functions. That can be handled with the > usual "warn for awhile" mechanism. The array module could be used > to manipulate mutable arrays of 8-bit data. While permeating the > Python innards with Unicode objects would be a major change I don't > see any big syntactic changes - or is that not what worries you? No syntactic changes, no. But the way we do things would become significantly different. And think of binary I/O vs. textual I/O -- currently, file.read() returns a string. Code dealing with binary files will look significantly different, and old code won't work. --Guido van Rossum (home page: http://www.python.org/~guido/)
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