Re: [Pyobjc-dev] buildapplication strawman
Brought to you by:
ronaldoussoren
From: Just v. R. <ju...@le...> - 2002-11-20 19:11:26
|
Jack Jansen wrote: > > I think that Python embedders should think twice about embedding > > based on an install not included with the system: the above is > > definitely not the only reason things may break. If you embed, ship > > Python as well and be done with it. > > I fail to see this... In the case of MacCVS it's simple: if there's no > framework Python installation you get no scripting capabilities. Sure, it's sortof an addon. I really don't see the point in worrying too much about embedders: X applications embedding Python will depend on Y versions/installtypes of Python, and I very much doubt that Y will ever be closer to 1 than to X. Might as well ship your own Python and get a _lot_ less support request from your users. > In the case of the Python OSA component I'm not sure what happens, > but it doesn't really matter: the Python OSA component should be > considered an integral part of the Python distribution (and we also > don't really care what the IDE does if Python isn't installed). I don't really see this as an app embedding Python: it's an environment which can work with Python if it's installed. If Python is optional, you're not really embedding... I'm thinking more of apps that _depend_ on Python, and for such apps a separate Python install is simply a common source of errors. I _know_, I've been there with Robofog. Later we shipped two versions: one depending on a separate MacPython install and one with a truly embedded Python. We got countless (install) error reports from (experienced!) end users using the former and none from people using the latter. Just |