Re: [Pyobjc-dev] buildapplication strawman

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

Jack Jansen wrote:

> > I read your code, and it just picks an arbitrary nib if there are
> > more than one, I don't quite understand how you can defend that...
> 
> No, not an arbitrary one, it picks the first one you specified. But
> never mind: let's do this your way (i.e. specify the nib by name,
> separate from the ..plist files).

Ah, whoops, sorry for the misunderstanding!

> >> But unfortunately the __rawmain__ trick is needed for one of the most
> >> useful applications of an applet: taking a standard unix Python
> >> script and turning it into a droplet.
> >
> > Don't you want to move the argv emulation to Python as well? It's
> > hairy stuff and I think we could win a great deal to have it in
> > Python. I really think we should strive to use a vanilla main, and
> > the execve wrapper makes it all possible.
> 
> Let me borrow Guido's time machine .... [POOF] Done!
> 
> PythonW uses the normal unix main program (as of 2.3a0, not in
> 2.2.X). And the __rawmain__ is all about doing the OSA stuff for
> argument emulation.
> 
> Look at Mac/Lib/appletrawmain.py (which is copied to __rawmain__ in
> an applets that wants argv emulation) and argvemulator.py (which does
> the actual work).

Ah, perfect, I hadn't realized that! Very cool. But then I don't  understand
what you meant with your comment about the "__rawmain__ trick" being needed: the
question was whether it is needed in the _actual_ compiled main program, but I
don't see how that could be the case with the execve wrapper.

Just