This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jjlee
Recipients jjlee
Date 2008-03-21.23:16:16
SpamBayes Score 0.15495867
Marked as misclassified No
Message-id <1206141378.11.0.857343736887.issue2451@psf.upfronthosting.co.za>
In-reply-to
Content
The new timeout support in 2.6 makes use of new function
socket.create_connection().  socket.create_connection() provides no way
to disable timeouts, other than by relying on socket.getdefaulttimeout()
returning None.  This is unfortunate, because it was the purpose of the
new timeout support to allow control of timeouts without reliance on
global state.

setdefaultsocket.create_connection() should always call
sock.settimeout() with the timeout passed to create_connection(), unless
a special non-None value is passed indicating that the global default is
to be used.  Specific modules may then use that special non-None value
where required, to preserve backwards-compatibility.
History
Date User Action Args
2008-03-21 23:16:18jjleesetspambayes_score: 0.154959 -> 0.15495867
recipients: + jjlee
2008-03-21 23:16:18jjleesetspambayes_score: 0.154959 -> 0.154959
messageid: <1206141378.11.0.857343736887.issue2451@psf.upfronthosting.co.za>
2008-03-21 23:16:17jjleelinkissue2451 messages
2008-03-21 23:16:17jjleecreate