strawman at astraw.com
Sat Feb 5 13:30:14 CST 2005
Just a minor point, but I think the bdist_mpkg extension to distutils
by Bob Ippolitto as part of py2app actually solves a lot of the
problems you describe for Mac OS X.
On Feb 5, 2005, at 2:09 AM, konrad.hinsen at laposte.net wrote:
> On 04.02.2005, at 23:53, Chris Barker wrote:
>> Actually, I disagree. Apple's Python is a better choice (you can't
>> run Aqua applications from a fink python, at least I don't think so),
>> but we do need to do more to provide easy to install packages for it.
>> (there are a lot)
> I don't care for Aqua as much as I care for all those nice Python
> packages I use every day. With Apple's Python, it's command line
> installation (which I don't mind, but many of my users do), or
> PackageManager for a select few packages. And I can't my own without
> proving my own Web server as well, so package contribution is
> effectively discouraged.
>> there aren't all that many people using OS-X developing Python
>> packages, and Apple has, of course, made OS-X just different enough
>> from other unices to require some work (or take the easy way and use
>> fink, but then it
> Not really, you can do command-line installation ("python
> setup.py...") just like on any other Unix, usually without any
> modification. The problem is that Mac users expect installers.
> It should be possible to extend distutils for making Mac installers
> just like it can make RPMs and Windows installers. I suppose nobody
> looked into this because the Apple Python community is divided into
> those who come from the Unix world and go for Fink, and those who come
> from pre-10 MacOS and go for MacPython plus PackageManager.
More information about the Numpy-discussion