Created on 2003-11-04 21:13 by vdvo, last changed 2009-04-05 18:25 by georg.brandl. This issue is now closed.
| Messages (4) | |||
|---|---|---|---|
| msg18901 - (view) | Author: Vaclav Dvorak (vdvo) | Date: 2003-11-04 21:13 | |
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. |
|||
| msg18902 - (view) | Author: Thomas Heller (theller) *  |
Date: 2003-11-05 07:37 | |
Logged In: YES user_id=11105 Sorry, no time for this now. |
|||
| msg82021 - (view) | Author: Daniel Diniz (ajaksu2) | Date: 2009-02-14 12:09 | |
Is this still present in NT-based Windows? Support for 98 was dropped in 2.6. |
|||
| msg85543 - (view) | Author: Georg Brandl (georg.brandl) * |
Date: 2009-04-05 18:25 | |
Let's assume it is Win9x-only. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2009-04-05 18:25:19 | georg.brandl | set | status: open -> closed dependencies: - Inappropriate error received using socket timeout superseder: Inappropriate error received using socket timeout nosy: + georg.brandl messages: + msg85543 resolution: out of date |
| 2009-02-14 12:09:25 | ajaksu2 | set | nosy:
+ ajaksu2 dependencies: + Inappropriate error received using socket timeout messages: + msg82021 title: socket.send() on behaves as nonblocking when timeout is set -> socket.send() on Win98 behaves as nonblocking when timeout is set stage: test needed |
| 2008-01-20 18:59:21 | christian.heimes | set | type: behavior versions: + Python 2.6, - Python 2.3 |
| 2003-11-04 21:13:22 | vdvo | create | |