Bob Ippolito wrote: > On Jul 20, 2006, at 5:11 PM, Christopher Barker wrote: >> Again, I see the need for py2app to be able to create "applets" --
> What exactly are applets supposed to be anyway? I'm not sure what you'd > want that isn't already covered by py2app... I wrote that because I remembered that you once specifically said that you didn't see the need for it, and thus wouldn't write the code to do it. so i figured someone else had to write it. > --alias covers the "well I already have *all* the files installed" case This may be what I'm looking for. > --semi-standalone covers the "depend on installed Python" case I don't think I want this, as I thought it only worked with Apple's Python. > --site-packages covers the "depend on some third party stuff being > installed" case > > The only caveat I guess is the latter case, because you will have to > explicitly set up a list of third party packages in your excludes. That may be perfect. I'll give them a try. Sorry to ask about something i could have found out myself. >> By the way, Bob, thanks for the new py2App, it seems to be working well. >> Is there a way to get it (and setuptools) in?: >> >> pythonmac.org/packages > > No, and I already answered that (twice-ish): > > http://mail.python.org/pipermail/pythonmac-sig/2006-July/017836.html > http://mail.python.org/pipermail/pythonmac-sig/2006-July/017839.html Right, you did answer the setuptools question. As for putting Py2app there, you made it clear why I couldn't make a mpkg, but I didn't' think that meant it was impossible. From the first post: """ setuptools should be installed using its own means so it can properly upgrade itself. bdist_mpkg packages aren't really compatible with eggs """ This is a problem. When we all had that that big "What should the 'official' python be on OS-X" discussion a while back, it seems there was a consensus that it would be good to have one supported python, and one supported repository of packages for it. Also that it should be as "point and clicky" as possible. That's what the repository at pythonmac.org is, and I think that it's a good start, now that we have a useful number of packages there, and I've been doing my tiny bit by contributing what I can. However, Py2App is a critical component, and it's really too bad to not have a way to make it available the same way. In part of that conversation, it was proposed that it would be good to have a GUI tool that was a front end to setuptools: i.e. something that would come up when you clicked on an .egg. I suppose once we did that, we could go to having .eggs, rather than .mpkgs as the standard way to distribute modules on Python. Of course, none of that happens until someone that knows what they are doing, and has the time, writes the code. it would be nice to have a goal in mind, however. Maybe we could at least have a mpkg for easy_install on pythonmac.org in the meantime (or have it be part of the main Python package). -Chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [EMAIL PROTECTED] _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
