Bill Janssen wrote: > That's certainly the prescribed behavior for the C stdio streams on > POSIX-compliant systems. I think a lot of the original design of the > Python I/O system was based on that C stdio system, including names > like stdin, stdout, and stderr. > > Now that we've moved away from the C stdio model, and the distinction > between text and binary streams is meaningful even on POSIX systems, > perhaps we should also change those names to reflect that difference > from C. Given that Py3K is a once-in-a-decade chance to break > backwards compatibility, and all. Perhaps something like > sys.io.input, sys.io.output, sys.io.err, or something similar. >
+1, except I'd say "sys.io.error"for the latter. -- Uche Ogbuji http://uche.ogbuji.net Founding Partner, Zepheira http://zepheira.com Linked-in profile: http://www.linkedin.com/in/ucheogbuji Articles: http://uche.ogbuji.net/tech/publications/ _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
