Enji Cooper <yaneurab...@gmail.com> added the comment:
?! Being blunt: why should opening a file in binary vs text mode matter? POSIX doesn't make this distinction. Per the pydoc (https://docs.python.org/2/library/functions.html#open): > The default is to use text mode, which may convert '\n' characters to a > platform-specific representation on writing and back on reading. If this is one of the only differentiators between binary and text mode, why should certain types of seeking be made impossible? Having to stat the file, then set the cursor to the size of the file, minus the offset breaks the 'seek(..)' interface, and having to use 'rb', then convert from bytes to unicode overly complicates things :(. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue36111> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
