Re: [Pyobjc-dev] flattening of module/packaging structure
Brought to you by:
ronaldoussoren
From: b.bum <bb...@ma...> - 2003-08-22 16:42:02
|
Did you add the various PyObjC modules to your project or did you use one of the templates? It sounds like that the folder reference in PBX/Xcode is no longer a folder reference, but a hierarchy of file references. Look in the target inspector and see what files are listed in Resources or the Copy Files phase. If it is everything, then your reference is broken -- remove all the pyobjc stuff and re-add, making sure to only create references for the top level folders! This particular features within PBX confuses the heck out of a lot of people -- not limited to PyObjC, by any means. b.bum On Thursday, August 21, 2003, at 12:41 PM, Zachery Bir wrote: > I think the problem with my app distribution is that when it is built > out, __main__.py has this: > > from PyObjCTools import AppHelper > > but on the Filesystem, this is what gets built: > > ~/Desktop/ZopeEditManager v0.5/ZopeEditManager.app/Contents/Resources > zbir@gorilla $ ls > AppHelper.py test_nsarray.py > AppHelper.pyc test_nsarray.pyc > . > . > . > __main__.py test_nsobject.pyc > > So, the package hierarchy is lost, and the app can no longer import > "AppHelper" from "PyObjCTools". > > Is this a bug? Or am I just at a running stumble? :) > > Zac > > > > ------------------------------------------------------- > This SF.net email is sponsored by: VM Ware > With VMware you can run multiple operating systems on a single machine. > WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines > at the same time. Free trial click > here:http://www.vmware.com/wl/offer/358/0 > _______________________________________________ > Pyobjc-dev mailing list > Pyo...@li... > https://lists.sourceforge.net/lists/listinfo/pyobjc-dev |