RE: Python/NT and winsock under win32s

Hammond, Mark (MHammond@jm.cmutual.com.au)
Fri, 10 Feb 95 16:11:00 PST

> Has Anybody had any luck getting "import socket" to work under win32s
(forme,
> WfWG 3.11 and trumpet winsock). I always get
>
> ImportError: DLL load failed with error code 87
Nope - sorry! However, for our main project, we need to get it going RSN.
Im not at all sure what the problem is here - I have never even looked into
it. Sam Rushing drew the short straw, and will be tackling that issue.
>
> Not that it would do much good anyway, unless somebody has a fix to
> make sock.makefile() to work. All the lib stuff (nntplib, ftplib, etc.)
> rely on makefile() to map the socket to a file.
Yeah. This is a bummer. Ron Forrester (?) (rjf@aurora.pcg.com) had a
solution for this that only works on NT. I think the only win32s way to do
this will be another hack, similar to what has been done on the mac by
Jack@cwi.nl (?).

> Is this package still evolving? I'd love to write something like a
newsreader
> or an empire client with python.
This package is evolving fast - so fast that my biggest problem has been
stabalising changes to release. Since the last release there is a source
level debugger, an object browser, full dialog support (buttons, listboxes,
combo-boxes etc) and many other nifty features.
And BTW - we _love_ the idea for a newsreader - because that is exactly what
we are building. The project I am working on started as a C++ newsreader
project. Then we started looking for an extension language to use, and
discovered Python. We were so impressed, we decided to avoid C++ whereever
possible! PythonWin is basically a development tool/environment for our
newsreader (but we have tried to keep it as a generic development tool for
Python).

As I have said in the last few posts, a new version is just around the
corner.

Mark (Mhammond@cmutual.com.au)