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. | [EMAIL PROTECTED] +--------------------------------------+ _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
