building Python under Services for Unix (SFU)

[Rich Krauter]

>(I am aware that there is a Windows version of
Python. >But it expects the

Windows syntax for paths, not the Unix/SFU paths. And >for all I know thereare other incompatibilities as well.)

Do you have to use SFU for some reason? If not, try
cygwin - see http://www.cygwin.com. You don't have to
build python from sources (just make sure python is
selected during the install process), and you can
install lots of other things sfu doesn't include.

Rich

__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html

[Mike Maxwell]

Rich Krauter <rm*******@yahoo.com> wrote in message news:<ma*************************************@pyth on.org>...

Do you have to use SFU for some reason? If not, try
cygwin ...

I had moved to SFU from CygWin, thinking there might be an advantage
(speed, NFS access, etc.) In the end, I decided the disadvantages
(not having a Python that used the unix-style directory structure,
lack of some other utilities I depended on) outweighed whatever
advantages there might be, and reverted to CygWin.

I think the moral of the story for Microsoft is that they have some
work to do to make SFU a competitor. At least that's my view; I may
be missing something.

Mike Maxwell

[Martin v. Löwis]

Mike Maxwell wrote:

I think the moral of the story for Microsoft is that they have some
work to do to make SFU a competitor. At least that's my view; I may
be missing something.

Certainly: The Interix subsystem is just one part of SFU, other parts
being the servers (NFS, NIS, etc). Those have no competition from
Cygwin.

As for the Python port to Interix: Somebody would have to contribute
the port to Python (sf.net/projects/python), just as people had to
actively contribute a cygwin port (and that was not easy to write,
either). Whether it is Microsoft's job to make this contribution
is debatable.

Regards,
Martin