Re: [Pyobjc-dev] Newer NibLoader.py

[Just v. R. <ju...@le...>]

Jack Jansen wrote:

> Is there a reason you like yours better than mine, or does it somehow 
> suit PyObjC better (I haven't looked at it for aeons... something like 
> 3 weeks:-)?

Yours checks for four filenames in Resources, whereas for a pyobjc project we
can just hardcode the main program from a template. Hm, you could do that, too
;-)

Yours is nicer in that it checks the existance of the main program.

> I would definitely prefer the MacPython and the PyObjC version of the 
> script to be the same, so if there's a good reason to use this one for 
> PyObjC I'll change the MacPython applet structure to use the name 
> realmain.py too (but convince me first:-).

Sorry, "realmain.py" is by no means a serious suggestion. I think it should read
%(mainprogram)s ;-)

> For people who don't track Python CVS: the difference is that in my 
> version I do
> for name in ["__rawmain__.py", "__rawmain__.pyc", "__main__.py", 
> "__main__.pyc"]:
> around the os.path.join(....., name). This gives me the current applet 
> naming scheme (__rawmain__, if it exists, will read AppleEvents for 
> ODOC's and stuff them into sys.argv and then call __main__, which can 
> then be a normal unix-style script but still get the files the user 
> dropped on the applet in sys.argv).

I was wondering about that: where do you do your argv emulation if not in _this_
little program? And if here, then you might as well use two templates. Or
three...

Just my 2c.