On 09/13/12 08:51, MRAB wrote:
> I get this:
>
> Python 2.4.4 (#71, Oct 18 2006, 08:34:43) [MSC v.1310 32 bit (Intel)] on
> win32
> Type "help", "copyright", "credits" or "license" for more information.
> >>> data = file(r'C:\Python24\DLLs\_socket.pyd', 'rb').read()
> >>> import md5
> >>> md5.
On 2012-09-13 14:35, Tim Chase wrote:
On 09/13/12 08:12, MRAB wrote:
I've just downloaded, installed and tested Python 2.4.4. No crash.
This is with Windows XP Pro (32-bit).
Could I get the MD5 of your $PYTHONDIR\DLLs\_socket.pyd to see if it
matches mine?
data = file('_socket.pyd', 'rb').r
On 09/13/12 08:12, MRAB wrote:
> I've just downloaded, installed and tested Python 2.4.4. No crash.
>
> This is with Windows XP Pro (32-bit).
Could I get the MD5 of your $PYTHONDIR\DLLs\_socket.pyd to see if it
matches mine?
>>> data = file('_socket.pyd', 'rb').read()
>>> import md5
>>> md5.md5(
On 13/09/2012 13:42, Tim Chase wrote:
I'm not sure if this is some Win32 update that was silently applied
by our netadmin, but when I simply "import socket" at the command
line, it's crashing (with the "Do you want to send this information
to Microsoft" debug/crash dialog).
It was working as of
On 09/13/12 07:42, Tim Chase wrote:
> It was working as of last night, and to the best of my knowledge,
> nothing was changed on the system. It took a while to track it
> down, but it came from importing smtplib which in turn imports socket.
>
> I've tried "import socket" and it crashes, but then
I'm not sure if this is some Win32 update that was silently applied
by our netadmin, but when I simply "import socket" at the command
line, it's crashing (with the "Do you want to send this information
to Microsoft" debug/crash dialog).
It was working as of last night, and to the best of my knowle
