Lukáš 'Spike' Polívka wrote: > When running the app or building an alias bundle, I have to export > PYTHON_PATH and use --use-pythonpath flag, after that, it works. When > building a deployment bundle, it does not work.
This MAY be a hint. When py2app does its thing, it moves all the modules it thinks you need into the app bundle. What that means is that the path to them all is different than when you run it outside the bundle. I've found that any funny business with PYTHON_PATH or sys.path can cause problems with py2app. In Alias mode, it's possible that the bundled app can still find stuff that wasn't included in the bundle, since it's pointing to the original source anyway. What's worked for me in the past is to make sure that sys.path matches what you need when setup.py is being run -- so you need to make sure whatever you do to get it right in your app is also done in setup.py. That may not have anything to do with your issue -- I'm confused as to why a module in setuptools is needed at this stage. However, I don't think py2app supports using eggs completely anyway, so maybe you've got something installed as an egg that you could install the old-fashioned way instead. -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [EMAIL PROTECTED] _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
