On Feb 8, 2005, at 12:57, Chris Barker wrote:
Bob Ippolito wrote:On 8-feb-05, at 15:51, Brendan Simons wrote:
My question: can I use py2app to build a redistributable app that's statically linked to either package manager's libraries? Or do I have to install Fink/DarwinPorts on each of my clients' machines?
If you are distributing a single substantial application, py2app is probably the way to go. However, if you are distributing a set of apps, you may not want each one to have a complete copy of everything, so...
Eh, you probably want them to for everything but the most controlled environments. Bandwidth and disk space is cheaper than support hassles.
(I would like to develop an app that uses numeric, scientific python, wxPython, and matplotlib, which are all somewhat difficult to install by hand, but are all readily available via Fink or DarwinPorts)
The Fink and Darwinports versions of these will give you X11 versions (particularly wxPython), which you may not want (Someone please correct me if I'm wrong). In fact, if you use fink, you may get it all working with the fink Python. Will py2app bundle a fink python app? And as Bob pointed out, fink, at least, will give you a bunch if libs that duplicate ones that are included with a stock OS-X
py2app is compatible and tested with darwinports, which means that it should also work with Fink, unless they screwed something up :)
As to the "difficult to install":
Numeric is easy, with either setup.py build (once it's fixed...argg!), or even easier, with the mpgk that Bob put out.
matplotlib is now easy, thanks to the mpkg that I just put together (only works with Agg and wxPython at the moment, though poorly tested with wxPython. I'm planning on making a GTK and TK compatible version soon, anyone want to help?). Bob, if you're reading this, could post the link?
SciPy is probably a pain in the $^%^&. I haven't tried it recently. However, my goal is to make an nice OS-X package of this as well. I'm looking for folks to help with that.
My impression of fink (and darwinports may be different, I'll be checking that out) is that it's kind of an all-or-nothing proposition. If you want a Linux-like system, running in parallel to OS-X, on the same kernel, you'll be quite happy. If you want it to feel like it's part of OS-X you won't. Being a Linux geek, you'd think I'd be happy with the former, but frankly, If I want Linux,. I'll run Linux (and I do). On OS-X I want OS-X, and, more importantly, folks I work with, that I give apps too, don't want to have anything to do with Linux, command lines, X11, or figuring out apt-get.
Darwinports is a lot less all-or-nothing. I have very few things activated from darwinports at a given time and it works and interoperates with the rest of the stuff I have rather well.
I really think we can get a complete set of OS-X friendly packages out for all to use. it's really not all that hard, once you've got the tricks figured out. We'll have a MUCH easier time getting folks to use python on OS-X if we have nice friendly binaries for them to install.
I agree.
By the way, what is the status of Package Manger, and the two repositories (Jack's and Bob's) Are they being maintained? should I submit matplotlib to them?
Mine is not. I'm going to toss it in favor of a mpkg and/or egg based solution when one is ready.
If anyone want to help with my SciPy on OS-X project, please let me know. There is some real momentum in the NumPy/SciPy crowd to make SciPy easier to install right now.
Well, if it will build, bdist_mpkg will package it..
-bob
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
