Re: [Pyobjc-dev] Python rather than ObjC for main?
Brought to you by:
ronaldoussoren
From: Ronald O. <ous...@ci...> - 2002-11-13 07:40:33
|
On Tuesday, Nov 12, 2002, at 16:43 Europe/Amsterdam, bb...@ma... wrote: >> Done. Main.py is now __main__.py? Good idea. My only problem with >> the current scheme is that you have to add import statements for your >> source. Is there away this could be automatically, or better yet >> dynamically? It would be nice if the user didn't have to touch >> __main__.py manually. It would be even nicer if __main__.py could >> figure out where the other stuff is itself. > > It would be nice if the __main__.py could have a bunch of the > repetitive code ripped out. Wouldn't be hard; the whole framework > bootstrapper could be moved to the AppKit module as an extension and > that is the bulk of the code. > It might be usefull to make __main__.py a part of pyobjc that is copied into the application and use that to load the 'PrincipalPythonFile'. That way we can perform all magic that is needed to startup the .app without bothering the user with it (e.g. user code would keep working if/when we move to a CFBundleExecutable with an embedded python). Ronald |