[Pythonmac-SIG] py2app standalone options (original) (raw)

Bob Ippolito bob at redivi.com
Sun Dec 26 20:20:57 CET 2004

On Dec 26, 2004, at 10:46 AM, has wrote:

Bob Ippolito wrote:

The goal for 0.2.0, which I think has already been achieved (sans documentation), was to make it better than the alternatives for any platform. When do you think we'll start seeing some formal documentation for py2app?

Write some and I'll include it. Right now the only documentation I'm working on is PyObjC, which does include some py2app related documentation.

Look at all this another way: in an ideal world, developers and their applications wouldn't need to deal with any of this dependency crap at all. Each app would merely list its requirements and the system would magically conjour up suitable components upon request.

In order for that to happen, either every user will have to have every version of every library already installed, or they would have to have the newest version of every library already installed (assuming that libraries would never be able to break backwards compatibility). Hardly. All you need is a CPAN-style central repository and a runtime extension that knows how to look it up and download components on-demand.

That doesn't fix the multiple versions problem.

You can already have that if you want it, but none of them are perfect and none of them are suitable for the common user on Mac OS X. Which is not to say that such a system could not be made suitable for the common user. All it needs is a will, and a really solid grasp of HCI (something OSS often isn't as strong on, but that's not insoluble either).

It takes more than knowing how and wanting to do something to make it happen :)

-bob

More information about the Pythonmac-SIG mailing list