[issue7145] UTF-16 BOM is not written by socket.makefile (but is expected by read)

Antoine Pitrou added the comment: Indeed, I would suggest won't fix. -- resolution: -> wont fix status: pending -> closed ___ Python tracker ___ _

[issue7145] UTF-16 BOM is not written by socket.makefile (but is expected by read)

Serhiy Storchaka added the comment: Won't fix? -- nosy: +serhiy.storchaka status: open -> pending ___ Python tracker ___ ___ Python-bug

[issue7145] UTF-16 BOM is not written by socket.makefile (but is expected by read)

Antoine Pitrou added the comment: The explanation is that sockets are not seekable, but the heuristic to decide whether to write a BOM relies on tell() to return 0 on start-of-file. If we unconditionally wrote a BOM, there would be a risk of duplicate BOMs depending on the use case, which is mor

[issue7145] UTF-16 BOM is not written by socket.makefile (but is expected by read)

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue7145] UTF-16 BOM is not written by socket.makefile (but is expected by read)

Yang Zhang added the comment: To answer my own question: specify UTF-16BE or UTF-16LE -- ___ Python tracker ___ ___ Python-bugs-list m

[issue7145] UTF-16 BOM is not written by socket.makefile (but is expected by read)

New submission from Yang Zhang : When I call s.makefile('r',encoding='utf-16').read(), this expects a BOM, but s.makefile('w',encoding='utf-16').write('hello') doesn't produce it. This is asymmetric. BTW is there a way to prevent the reading file from expecting a BOM? -- components: L