Mail Archives: djgpp/2002/05/19/18:15:15
> Wow! How difficult was it to port? Were any source changes required?
A little. I'm not that good, and I needed some help. But it seems OK now,
all the scripts seem to work. I wrote a *small* README outlineing some of
the steps needed to set it up. If anyone has trouble, please let me know in
this group, because I have decided not to announce it *just* yet to the
python guys(and gals - sorry Eli) :-)
Actually, I did it because I was looking for a faster alternative to Batch
files.
> > Richard Dawe's libsocket port may enable some low-level options,
but
> > socketmodule.c still does not compile as of now. Libsocket is not being
> > actively developed.
> [snip]
>
> Personally I would not bother trying to make Python work with libsocket,
since
> libsocket is unsupported. It's more trouble than it's worth. Is a socket
> library currently required to build Python?
I have Watt32 downloaded, but I haven't played with it yet. You know, Python
has a socketmodule, right? well... for it to work ... it needs a socket.
Socketmodule is missing entirely this go-around. maybe someday I'll find an
answer. BTW: thanks for keeping the Libsocket page up, even if you don't
support it anymore.
Ben
- Raw text -