[Python-Dev] Who understands _ssl.c on Windows?

Tue Apr 11 02:17:53 CEST 2006

[Tim Peters wrote]
> Trent (and anyone else who wants to play along), what happens if you
> do this by hand in a current trunk or 2.4 build?:
>> import socket
> s = socket.socket()
> s.settimeout(30.0)
> s.connect(("gmail.org", 995))
>> On my box (when gmail.org:995 responds at all), the connect succeeds
> in approximately 0.03 seconds, giving 29.97 seconds to spare ;-)

 C:\trentm\src\python\python\PCbuild>python_d
 Python 2.5a1 (trunk, Apr 10 2006, 14:48:00) [MSC v.1310 32 bit (Intel)] on win32
 Type "help", "copyright", "credits" or "license" for more information.
 >>> import socket
 [25133 refs]
 >>> s = socket.socket()
 [25145 refs]
 >>> s.settimeout(30.0)
 [25145 refs]
 >>> s.connect(("gmail.org", 995))
 [25145 refs]
 >>> 
Sorry that I took so long to run this. It is a little unfortunate that
with the last build step being "clean", I couldn't just cd into the
build directory and try to run this.
Seems like that was a good thing that I did take so long because it
passed in the most recent build :)
 http://www.python.org/dev/buildbot/trunk/x86%20W2k%20trunk/builds/371/step-test/0
> Can you identify a reason for why it times out on the Win2K buildbot? 
> (beats me -- firewall issue, DNS sloth, ...?)

It is possible that this was due to network changes that we are doing at
work here. We are preparing for an office move in a couple of weeks
(http://blogs.activestate.com/activestate/2006/02/free_as_in_will.html).
My eyes glaze over whenever the systems dudes mention VPN, SSH, DNS,
VMWare, sub-domains and DHCP in the same breath.
Trent
-- 
Trent Mick
TrentM at ActiveState.com