James Y Knight wrote:
> Hum, actually, it somewhat makes sense for the "open" builtin to
> become what is now "codecs.open", for convenience's sake, although it
> does blur the distinction between a byte stream and a character
> stream somewhat. If that happens, I suppose it does actually make
> sense to give "makefile" the same signature.
We could always give the text mode/binary mode distinction in "open" a real
meaning - text mode deals with character sequences, binary mode deals with
byte sequences.
Cheers,
Nick.
--
Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia
---------------------------------------------------------------
http://boredomandlaziness.blogspot.com
_______________________________________________
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
