Just van Rossum wrote:
> Greg Ward wrote:
>>
>> -1 on using a file mode character that conflicts with existing
>> conventions (eg. if "t" really is already used on Windows, find
>> something else).
>
> The "t" isn't really needed to begin with, files opened in text mode should
> convert any line ending to \n. One of Jack's arguments _for_ "t" is:
>
> - Compatibility. Programs which already do their own
> interpretation of \r\n in text files would break. Programs
> which open binary files as text files on Unix would also break
> (but it could be argued they deserve it :-).
You misunderstood Greg: he wants to have "t" but use a different
character to represent it. Maybe "p", for Python text mode. ;-)
--
--- Aahz (@pobox.com)
Hugs and backrubs -- I break Rule 6 <*> http://www.rahul.net/aahz/
Androgynous poly kinky vanilla queer het Pythonista
We must not let the evil of a few trample the freedoms of the many.
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