[Pythonmac-SIG] Re: Pythonmac-SIG digest, Vol 1 #929 - 12 msgs

[Jack Jansen]

Recently, Donovan Preston <dp@ulaluma.com> said:
> OS X already has an implementation of socket-based IO -- it's called 
> BSD. :-) And OS X already has a Python which will compile to use it -- 
> command line Python. What OS X Python is missing, therefore, is the IDE 
> running on top of the command-line Python binary. Stay tuned, hopefully 
> we'll have it soon. See my message about Mach-O MacPython IDE if you're 
> interested in knowing more.
> 
> first files, etc.)?  An alternative thought I have to work on is "how 
> hard
> will it be to glue the OS X CL interpreter (not MacPython) to PEF a 
> gaggle
> of libs?"  It looks doable but I've never traveled this road before.

This isn't worth it. We discussed it about a year ago (both here and
on the GUSI list) and by getting the BSD sockets you would also get
(unless you do major surgery) all the rest of glibc, so you would get
Unix filenames, Sioux would go down the drain, etc.

And you'd end up with something almost identical to MachoPython, but
with a funny (and slower) CFM component.

It's better then to do away with MacPython altogether and base
something on MachoPython. And that's also what is being worked on,
with porting all the modules, etc. (No doubt we'll call it MacPython
when it's finished, but for the time being it's better to make a
distinction between MacPython (CW-based Python with PythonInterpreter
and IDE which runs on 9 and X) and MachoPython (basically unix command
line Python with frameworks and Carbon modules and the rough
Python.app added)).
--
Jack Jansen             | ++++ stop the execution of Mumia Abu-Jamal ++++
Jack.Jansen@oratrix.com | ++++ if you agree copy these lines to your sig ++++
www.cwi.nl/~jack        | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm