Re: [Pyobjc-dev] Detecting Python interpreters on startup

[Bob I. <bo...@re...>]

On Friday, Sep 5, 2003, at 12:15 America/New_York, Ronald Oussoren 
wrote:

>
> On 5 sep 2003, at 18:06, Just van Rossum wrote:
>
>> Dinu Gherman wrote:
>>
>>> Yes, that's probably the best thing to do. I sniffed more into
>>> bundlebuilder now. On 2.3 it seems to use a modulefinder, ok... I
>>> wasn't quite aware how cool it is!
>>
>> Actually, it does so with 2.2 as well, provided modulefinder.py is
>> installed. The only thing it can't use with 2.2 is zipimport, so 2.2
>> .app bundles are somewhat larger.
>>
>> Ronald: I think modulefinder.py should be included with PyObjC in
>> MPCompat, next to bundlebuilder.py and plistlib.py. Would you agree?
>
> I do, please check it in. The --standalone option is very usefull.
>
> BTW. I don't think useing 'whatever python the user has installed' 
> would be useful, unless you don't test applications before releasing 
> them :-)

Yeah, other than saving bandwidth there is no good reason to NOT 
include a tested and working version of Python with your executable.

You can say on the distribution page:
	download SMALLER VERSION if you have OS X 10.3 installed, or have 
installed MacPython 2.3 yourself in OS X 10.2.X
	download LARGER VERSION otherwise

Most people have bandwidth to spare these days.  On the distribution 
end, there's always SourceForge (assuming you're an open source 
developer).

It would be interesting if SMALLER VERSION would be able to detect if 
it is running on the proper system (maybe a C bootstrap, or python 2.2) 
before doing anything, and if it's not running on a capable system then 
it would pop up a dialog box with instructions for how to download the 
LARGER version or install MacPython 2.3.

-bob