[issue26292] Raw I/O writelines() broken for non-blocking I/O

STINNER Victor added the comment: I close this issue as duplicate of bpo-13322 which is older and has a longer history. -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> buffered read() and write() does not raise BlockingIOError _

[issue26292] Raw I/O writelines() broken for non-blocking I/O

Changes by raylu : -- nosy: +raylu ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mail

[issue26292] Raw I/O writelines() broken for non-blocking I/O

Martin Panter added the comment: Here is a patch documenting that RawIOBase.writelines() is undefined for partial writes and blocking errors, as mentioned in (1) above. The alternative of requiring write() to be retried would IMO be unfair to existing writelines() implementations. It also seem

[issue26292] Raw I/O writelines() broken for non-blocking I/O

Martin Panter added the comment: Victor, why did you change the title to specify non-blocking mode? I think blocking mode can also be handled at the same time. I propose: 1. In existing versions (2.7, 3.5): Document that it is undefined what IOBase.writelines() will do if a write() call does

[issue26292] Raw I/O writelines() broken for non-blocking I/O

Changes by STINNER Victor : -- title: Raw I/O writelines() broken -> Raw I/O writelines() broken for non-blocking I/O ___ Python tracker ___