Message3073
| Author | rluse |
|---|---|
| Recipients | amak, fwierzbicki, rluse |
| Date | 2008年03月09日.08:23:19 |
| SpamBayes Score | 0.15295282 |
| Marked as misclassified | No |
| Message-id | <1205051000.44.0.31801301417.issue1005@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I think that for the recv/recvfrom issue that this is a very reasonable
solution. Jython 2.2.2 will test this even more.
I still think there is problem with the send/sendto timeout. (I will
open a separate problem if you like, just let me know).
----------------------
import socket
s = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
print s.gettimeout()
s.settimeout(1.0) # settimeout here done before the sendto
print s.gettimeout()
s.sendto('testdata', ('192.168.1.103', 9876))
print s.gettimeout()
print 'The program hangs here, even though s.gettimeout = 1.0'
buf, addr = s.recvfrom(2048)
---------------------------------------------
When the settimeout is performed after the sendto, it works properly.
I suspect that when config is run, that it sets the timeout to default
which is None, but the value of timeout in for the script is still 1.0.
(By the way, because of this testing, I will be opening a problem with
Python 2.5.2 on Windows). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月09日 08:23:20 | rluse | set | spambayes_score: 0.152953 -> 0.15295282 recipients: + rluse, fwierzbicki, amak |
| 2008年03月09日 08:23:20 | rluse | set | spambayes_score: 0.152953 -> 0.152953 messageid: <1205051000.44.0.31801301417.issue1005@psf.upfronthosting.co.za> |
| 2008年03月09日 08:23:20 | rluse | link | issue1005 messages |
| 2008年03月09日 08:23:19 | rluse | create | |
Supported by Python Software Foundation,
Powered by Roundup