[Python-bugs-list] [ python-Bugs-836058 ] socket.send() on behaves as nonblocking when timeout is set

SourceForge.net noreply at sourceforge.net
Wed Nov 5 02:37:46 EST 2003


Bugs item #836058, was opened at 2003-11-04 22:13
Message generated for change (Comment added) made by theller
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=836058&group_id=5470

Category: Windows
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Vaclav Dvorak (vdvo)
>Assigned to: Nobody/Anonymous (nobody)
Summary: socket.send() on behaves as nonblocking when timeout is set

Initial Comment:
When a timeout is set on a connected socket, the
socket's send() method behaves as if non-blocking mode
was set: when not enough buffer space is available, it
raises socket.error(10035, 'The socket operation could
not complete without blocking'). Instead, it should
block up to the specified number of seconds and only
then raise a socket.timeout exception if the data still
wasn't sent. This is with Python 2.3.2-1 on Windows 98.
On Linux, it works as expected.

Bug 805194 might be related.

----------------------------------------------------------------------

>Comment By: Thomas Heller (theller)
Date: 2003-11-05 08:37

Message:
Logged In: YES 
user_id=11105

Sorry, no time for this now.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=836058&group_id=5470



More information about the Python-bugs-list mailing list