Gabriel Genellina wrote:
> En Wed, 09 Jul 2008 15:02:56 -0300, Mirko Vogt <[EMAIL PROTECTED]> escribi�:
>
>> it seems that the socket-module behaves differently on unix / windows
>> when a timeout is set.
> [...]
>> Now I will change the code slightly - to be precise I set a timeout on
>> the sock
En Wed, 09 Jul 2008 15:02:56 -0300, Mirko Vogt <[EMAIL PROTECTED]> escribi�:
it seems that the socket-module behaves differently on unix / windows
when a timeout is set.
[...]
Now I will change the code slightly - to be precise I set a timeout on
the socket:
# test.py
import socket
sock=
On 2008-07-10, A.T.Hofkamp <[EMAIL PROTECTED]> wrote:
> On 2008-07-09, Mirko Vogt <[EMAIL PROTECTED]> wrote:
>> Is that behaviour common or even documented? Found nothing.
> Second sentence in the socket module documentation:
>
> Note: Some behavior may be platform dependent, since calls are
> made
On 2008-07-09, Mirko Vogt <[EMAIL PROTECTED]> wrote:
> Is that behaviour common or even documented? Found nothing.
Second sentence in the socket module documentation:
Note: Some behavior may be platform dependent, since calls are made to the
operating system socket APIs.
So yes, what you found i
Hey,
it seems that the socket-module behaves differently on unix / windows when a
timeout is set.
Here an example:
# test.py
import socket
sock=socket.socket(socket.AF_INET,socket.SOCK_STREAM)
print 'trying to connect...'
sock.connect(('127.0.0.1',))
print 'connected!'
# executed on windo
