[Pythonmac-SIG] Extensions for static versus frame

[tmk]

Yo,

Overall, I'm really happy with Jack and Just design for Python 
install on Mac OS X, ie using a framework install. and a launcher 
app in (/Applications/Utilities).

I think Michael's suggestion for Python extensions is right on the spot.

They should go into a user-accessible place. And to me, the best 
place on Mac OS X is clearly the .../Application Support/Python 
folder under any  of the Machine, Network, or User domains (meaning 
MacPython should really look into each of theses places like any 
well-behave Mac OS X app).

Like Robin, I'd also be glad to contribute monetary support to the 
further advancement of a well integrated Mac OS X
Python especially the Cocoa/PB/IB integration.

= tmk =

On Wednesday, July 17, 2002, at 11:17 AM, Michael Hudson wrote:

> Jack Jansen <Jack.Jansen@oratrix.com> writes:
>
>> yes, it is. Just and myself had a session of heavy MachoPython
>> design last week, and here's what we've come up with. please
>> comment.
>
> A thought I had a while back.  Feel free to ignore it.
>
> What is the current opinion on extension modules?  Currently they tend
> to end up deep down in
>
> /Libary/Frameworks/Python.framework/.../site-packages/
>
> Wouldn't it be nice if one could build a loadable bundle type thing
> that could be installed alongside the framework, or in
>
> /Library/Application Support/Python
>
> or somewhere?  This could include headers for e.g. Numeric.
>
> Cheers,
> M.
>
> --
>   $ head -n 2 src/bash/bash-2.04/unwind_prot.c
>    /* I can't stand it anymore!  Please can't we just write the
>       whole Unix system in lisp or something? */
>                                        -- spotted by Rich van der Hoff
>
>
> _______________________________________________
> Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
> http://mail.python.org/mailman/listinfo/pythonmac-sig
>