Antoine Pitrou pit...@free.fr added the comment:
Was committed in r84887.
--
resolution: - fixed
stage: - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9854
Antoine Pitrou pit...@free.fr added the comment:
Of course, I should have been more clear.
What I meant is that there's no such thing as explicit and native as
setblocking() for plain files.
Indeed. It would probably be a nice addition, assuming it is portable
enough.
A BlockingIOError is
Antoine Pitrou pit...@free.fr added the comment:
The problem with RawIOBase.read is fixed in r84814.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9854
___
Antoine Pitrou pit...@free.fr added the comment:
Here is a patch.
The tests are only run for unbuffered objects (buffering=0), since the
behaviour of buffered objects is driven by BufferedReader and friends, not by
the wrapped SocketIO.
--
keywords: +patch
nosy: +giampaolo.rodola
Changes by Antoine Pitrou pit...@free.fr:
Removed file: http://bugs.python.org/file18883/sockio_nonblock.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9854
___
Changes by Antoine Pitrou pit...@free.fr:
Added file: http://bugs.python.org/file18884/sockio_nonblock.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9854
___
Giampaolo Rodola' g.rod...@gmail.com added the comment:
I've never used socket.socket.makefile so I'm not sure, but its documentation
says:
The socket must be in blocking mode (it can not have a timeout).
If the statement is there because EAGAIN/EWOULDBLOCK were originally raised
then it
Antoine Pitrou pit...@free.fr added the comment:
Le mardi 14 septembre 2010 à 23:19 +, Giampaolo Rodola' a écrit :
I've never used socket.socket.makefile so I'm not sure, but its
documentation says:
The socket must be in blocking mode (it can not have a timeout).
If the statement is
