[MAL] > File objects opened in text mode will use "t#" and binary > ones use "s#". [Greg Stein] > ... > The real annoying thing would be to assume that opening a file as 'r' > means that I *meant* text mode and to start using "t#". Isn't that exactly what MAL said would happen? Note that a "t" flag for "text mode" is an MS extension -- C doesn't define "t", and Python doesn't either; a lone "r" has always meant text mode. > In actuality, I typically open files that way since I do most of my > coding on Linux. If I now have to pay attention to things and open it > as 'rb', then I'll be pissed. > > And the change in behavior and bugs that interpreting 'r' as text would > introduce? Ack! 'r' is already intepreted as text mode, but so far, on Unix-like systems, there's been no difference between text and binary modes. Introducing a distinction will certainly cause problems. I don't know what the compensating advantages are thought to be.
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