Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <3CE93EB2.2DD59789@phekda.freeserve.co.uk>
Date: Mon, 20 May 2002 19:21:38 +0100
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.19 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: DJGPP newsgroup <djgpp AT delorie DOT com>
Subject: Re: ANNOUNCEMENT: Python 2.2.1 for DOS test release
References: <3ce7fc1f$0$26970$9b622d9e AT news DOT freenet DOT de> <3CE810BA DOT FCA8CEDF AT phekda DOT freeserve DOT co DOT uk> <3ce8232a$0$26959$9b622d9e AT news DOT freenet DOT de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

Hello.

deckerben wrote:
> 
> > 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) :-)

Do you have diffs against the original sources? I can take a look at the
diffs, if you'd like a second opinion.
 
(I added a DJGPP port of Python to my list of things to do on Friday, which is
a pretty strange coincidence!)

> Actually, I did it because I was looking for a faster alternative to Batch
> files.

That's a long way to go, just to get faster scripts! But I can understand
that.
 
> > >         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.

I haven't really started learning Python yet. I've done some Zope stuff and
I'm going to write some stuff at work in Python, but I'm not at all familiar
with the language.

The problem with socket libraries is that they only work on a subset of the
platforms that DJGPP runs on. That really is pretty inconvenient for the user.
Until there's one library for all platforms, I'm not sure it's worth trying to
add Socketmodule.

In the worst case a Python program could invoke a program to do what it wants,
e.g.: get a web page.

> BTW: thanks for keeping the Libsocket page up, even if you don't
> support it anymore.

It's no trouble. 8) Actually, I hope there are some useful bits of information
and links there.

Thanks, bye,

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]