Nick Coghlan wrote: > However, such a "future_builtins" module could still include modified versions > of those standard objects - such "future-proofed" code would simply still need > to deal with the fact that other libraries or clients may pass in the > old-style components (e.g. just as unicode-aware code needs to deal with the > fact that other libraries or clients may produce 8-bit strings rather than > unicode text). And be careful not to pass them to old code which expects the traditional versions of these objects. Sounds far too tricky and error-prone to be worth the trouble to me. -- Greg Ewing, Computer Science Dept, +--------------------------------------+ University of Canterbury, | A citizen of NewZealandCorp, a | Christchurch, New Zealand | wholly-owned subsidiary of USA Inc. | greg.ewing at canterbury.ac.nz +--------------------------------------+
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