[issue23351] socket.settimeout(5.0) does not have any effect

2015-02-04 Thread Charles-François Natali
Charles-François Natali added the comment: It's a kernel bug closing (working fine on my Debian wheezy with a more recent kernel BTW). -- resolution: -> third party status: open -> closed ___ Python tracker _

[issue23351] socket.settimeout(5.0) does not have any effect

2015-02-04 Thread Piotr Jurkiewicz
Piotr Jurkiewicz added the comment: Does not work on Debian 7 Wheezy, kernel 3.2.65. $ python test.py ('sending ', 0) took 0.000s ('sending ', 1) took 0.000s ('sending ', 2) took 0.000s ('sending ', 3) took 0.000s ('sending ', 4) took 0.000s ('sending ', 5) took 0.000s ('sending ', 6) took 0.000

[issue23351] socket.settimeout(5.0) does not have any effect

2015-02-02 Thread Charles-François Natali
Changes by Charles-François Natali : -- status: open -> pending ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23351] socket.settimeout(5.0) does not have any effect

2015-01-30 Thread Antoine Pitrou
Antoine Pitrou added the comment: The test script works on Ubuntu 14.10 as well. -- ___ Python tracker ___ ___ Python-bugs-list mailin

[issue23351] socket.settimeout(5.0) does not have any effect

2015-01-30 Thread Charles-François Natali
Charles-François Natali added the comment: > The way socket timeouts are implemented is by using select() to determine > whether the socket is ready for read/write. In this case, select() probably > marks the socket ready even though the queue is full, which later raises > EAGAIN. Indeed, and

[issue23351] socket.settimeout(5.0) does not have any effect

2015-01-29 Thread Antoine Pitrou
Antoine Pitrou added the comment: The way socket timeouts are implemented is by using select() to determine whether the socket is ready for read/write. In this case, select() probably marks the socket ready even though the queue is full, which later raises EAGAIN. About SO_SNDTIMEO and SO_RCVT

[issue23351] socket.settimeout(5.0) does not have any effect

2015-01-29 Thread Piotr Jurkiewicz
New submission from Piotr Jurkiewicz: After setting socket.settimeout(5.0), socket.send() returns immediately, instead of returning after specified timeout. Steps to reproduce: Open two python interpreters. In the first one (the receiver) execute: >>> import socket >>> r = socket.socket(sock