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 | ncoghlan at gmail.com | Brisbane, Australia
---------------------------------------------------------------
http://boredomandlaziness.blogspot.com
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