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

[Tim Peters]

[Trent]
>     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

Excellent!  Thanks to the buildbot's blamelist, we can definitely
conclude that your Win2K box's problem was cured by Andrew checking in
a change to whatsnew25.tex.  Works for me :-)

> ...
> 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.

Ya, life will get a lot better if you leave the sysadmins behind ;-) 
Good luck with the move and the heady wine of corporate independence,
BTW -- and be sure to visit the old folks on holidays.